SmartSDK

I have a fix for the next release of our SmartSDK solution that will require a maintenance signature.

1. We are still supporting devices containing a Smart Operation Panel with SmartSDK version 2.10 and later.
2. AppManager.zip, Authentication.zip, LrsLauncher.zip, and SecureDelivery.zip are the modified apps.
3. The .dalp files are not modified.

Changes:

1. Addressed issue of "Connection reset by peer".
2. Fixed an issue where the code wasn't being displayed on some Card and Code enrollment types.
3. Added ability to force job accounting to run when in internet-only mode.

Regards
Bryan

Hi

We want to actively detect when a Ricoh device changes its IP address.

We have checked SmartSDK documentation and only found:

• The "/rws/property/network" to inquire about network information in Web API. 
• The NETWORK_CONNECTED intent indicates the network connection.

The naive solution is to continuously call the Web API to get network info and then compare it with the previous call. But we want to find a better solution.

Is there a way/event the device notify the application when it changes its IP address?

Thank you.

I'm currently implementing the API on an Android app, and I've managed to send WebAPI requests but I'm having trouble understanding how events are received. Is it the printer sending events and we receive them on the Android end with a BroadcastReceiver? I'm not sure I understand what's happening in the CopySample sample app. I see the method setReceiveFunctionJobEvent, which is called by the start/endReceiveJobEvent methods. Do we need to send a broadcast to begin receiving events from the copier?

Hi there,

Attached is the ZIP file for the production signature. We have increased the application version from 1.4.0 to 1.5.0. In this update, we have done bug fixes found on testing. We have shared the unsigned .apk and dalp file and unsigned packages for certification. Please let us know if you need anything else from our side.

Thanks!

Hi,

I hope this message finds you well. We are currently in the process of developing an Android application for our clients, and we have encountered challenges in preparing a build that can be successfully installed on SOP G3.0 devices. I am reaching out to seek guidance and assistance in resolving this issue.

Note: We have already submitted our application in PTEC(ricoh-usa.com).

Typically, our lab testing involves the following steps:

Current Process:

1. Enter the Device Serial Number in the DEVELOPMENT KEY REQUEST form available at https://ricoh-ridp.com/forms/signatureservices/ricoh-smartsdk/development-keys.
2. Download the ricohdevelop.keystore and Manifest.mf files from the provided link.
3. Place the downloaded files inside the ant folder within our project structure.
4. Utilize the signWithDevKey function to prepare the signed build in Android Studio.

Unfortunately, this process is not yielding the desired results, as it is resulting in a J240 error for SOP G3.0.

As an alternative approach, we have generated an unsigned build and converted it to a beta signed build using the SmartSDK Signature Self Service available at https://ricoh-ridp.com/signature-self-service. While this beta signed build successfully installs on SOP G2.0 and SOP G2.5 devices, it encounters an error (J110) when attempting to install on SOP G3.0 devices.

We have also explored the Smart Operation Panel > Start Guide > Installation > 02. Signing by Developer section in the SmartSDK documentation. It mentions the requirement of the Manifest.mf, ricohdevelop.keystore, and password, which are expected to be provided by Ricoh. Could you please guide us on how we can obtain these files for build preparation? For your reference, I have attached an image illustrating our request.

Finally, we seek clarification on the correct process to prepare an Android build that will successfully install on SOP G3.0 devices.

We appreciate your prompt attention and assistance in resolving this matter. Thank you for your time and support.

Thanks,

Our customer is experiencing a problem with our application that we're unable to reproduce. First, they claim they've closed port 54080 & 54443 on their devices at the direction of their Ricoh support due to security concerns. I have not found a security advisory on this and have not been able to identify how this is configured. Our devices respond to these ports fine. If this is true, it's likely a problem. Our application uses this port to retrieve device model information. 

Specifically, a page in our application loads the attached script file in the devices NX web browser. That page makes a sideways call to the device's embedded web server with jquery to perform a GET request to this URL:

https://gw.machine.address:54443/rws/property/deviceInfo?_=r822oUL4

This is successful in our test lab. We've tried a number of URLS unsuccessfully in the customer's environment:

https://gw.machine.address:54443/rws/property/deviceInfo?_=HGmFOUHh
http://gw.machine.address:54080/rws/property/deviceInfo?_=FezuQFl
https://gw.machine.address/rws/property/deviceInfo?_=CO9RfB
https://localhost:54443/rws/property/deviceInfo?_=3ozveLh8
https://prtciclab2.wellsfargo.net/rws/property/deviceInfo?_=PEPKXaXV

They all return an error similar to:

NetworkError: Failed to execute 'send' on 'XMLHttpRequest': Failed to load 'https://prtciclab2.wellsfargo.net/rws/property/deviceInfo?_=7hx8ONOo'

Note that in the attached script ricoh.dapi.apiClient.setSSL() is called in the function initializeDeviceForLoginPage, then the XmlHttpRequest is sent in the function getDeviceInformation. The code is similar to ricoh.dapi.internal.getSerialNumber in ricoh.dapi.js. We're using jquery version 1.11.3.

In case this is a CORS issue, note that the application's web server does not respond with the Access-Control-Allow-Origin header and it is hosted on port 444 in the customer's environment and port 443 in our test lab.

Can you provide additional information about closing ports 54080 & 54443?

Hi

We have 2 G3 devices (IM 370F and IM 460F) but It seems both are using incorrect SmartSDK version, our application RicohSOP  is failed and hanged with a message "... is not responding" after installed on the device.

I checked device logs, it shows SmartSDK version 4.00.00, while the SmartSDK guide requires it is version 5.00.

Could you please confirm is this firmware correct? or do we need to request Ricoh Local Support to upgrade device firmware?

Please see the attached logs for IM 460 (IM 360 is the same log and issue).

Thank you

Ngoc

We are having problems signing our application package using the SignFish service and are hoping for some assistance. We are following the steps described on https://ricoh-ridp.com/signature-self-service but are receiving an error message that says, "Invalid Vendor ID". We are attempting this operation under product id 1667760129. There are a few noteworthy points here:

1. One of our developers inadvertently created a duplicate Product ID for an existing product. The duplicate product Id is 1711276422 (rf IDEAS Reader Plugin), this product is already represented by Id 1667760129 which is being used in production. Is it possible for you to remove the duplicate 1711276422 from the platform to avoid confusion?
2. Product Id 1667760129  was originally created with RIDP EMEA and "transferred" to RiDP NA through the help of John Verne.
3. We are able to successfully submit a signature request using PID 1711276422, but that isn't the PID we need to use moving forward (this plugin is deployed using rxop with the existing 1667760129 PID).
4. I have yet to test development signatures using the respective manifest with PID 1667760129. I will test this next.

I would also like to clarify my understanding of the non-production signature services:

Development Signature - A Manifest file and keystore for a Product ID are downloaded from Ricoh. We can use these artifacts to locally sign an APK/DALP Package, which can then be deployed to a Ricoh MFP via WIM/USB/RXOP. The plugin will only run on device serial numbers defined in the manifest file. Development signatures are used so developers can rapidly test and deploy plugin changes in their local environment; without having to submit anything to Ricoh.

Beta/Demo Signatures - Are restricted by time rather than serial number. These are generated using the Ricoh SignFish utility and are valid for 60 or 10 days respectively. Frequently used for customer demos or with the Ricoh Certification Process.

Thank you in advance,

Patrick

Request for maintenance signature, bug fixes and other enhancements.

This is a test.