SmartSDK

Hi,

Please find attached version 3.2.5 of the Papercut MF application for a maintenance signature.

The changes are described as follows:

• Fixed an issue that customized color scheme does not apply to some screens.

• Updated fax getfaxphonecontact rpc call to allow more parameters.

Also we have made sure the provided package does not have any pre-attached dev signature, thanks.

(Please note that we need a SHA-1 signature only, as our app runs on some older devices that do not support SHA-256.)

Thanks,

Hello Team,

We have couple of queries.

Issue 1:One of our customer using IM C6010. They are trying to install the attached prod signed package(UPConnector.zip). Installation fails with the below message(Error Code J240).

        Same package works fine on other models(Ricoh IM C300). Could you please resolve this issue? 

Issue 2:
        Also could please help on finding smart sdk version(Android version) on any Ricoh printer console/portal?
 

Hi support,

what do I need to know regarding Brands "Savin" and "Lanier" in terms of development?

Will SmartSDK work the same way on Savin and Lanier devices?

Thank you,

Luís

Request for maintenance signature, bug fixes and other enhancements.

Hi Team,

We have been using the older version of JRE to create a JVM environment at a hosted server with our Pharos Sentry embedded solution which is built upon SmartSDK i.e. 1.8.0_131 32-bit. We want to move this to 64-bit with the latest official JRE version. I want to check with you if replacing the JRE would impact any of the functionality or behavior concerning Libraries associated with SmartSDK and RXOP or if this would impact any legacy printers. 

Let us know if this would impact in any way. Or anything you would suggest we need to do here.

Thanks!

We have a customer that sees "Cleartext HTTP traffic to gw.machine.address not permitted" in their logs when trying to get scanner capabilities, and we're unable to initiate a scan. We've tried reproducing this ourselves, and were certain it was connected to the "Permit SSL/TLS Communication" setting, but we're unable to reproduce the issue with that set to "CipherText Only".

We've also verified with the customer that they are not using the "CipherText Only" setting.

Under what circumstances would a call to get the scanner capabilities return this error?

What else can we do to try to reproduce and correct the issue?

Please Product sign the application.

Hi,

We are currently in the process of developing a custom login application tailored for our esteemed customer. As part of this development, we are eager to incorporate NFC (Near Field Communication) login functionality into the application. However, despite our thorough search, we have encountered challenges in locating relevant developer documentation or sample applications within the SDK.

Considering your expertise in this domain, we kindly request your assistance in guiding us through the implementation of NFC authentication for Ricoh devices. Any insights, documentation, or sample applications you could provide would be immensely valuable to us in ensuring the seamless integration of this feature.

Your support in this matter would be greatly appreciated, and we eagerly await your response.

Thanks

I had opened a previous incident that was closed due to inactivity. The previous incident question was this:

"""

When a user clicks the 'check status' button on the SOP, the 'login' button disappears and it seems that login becomes unavailable at that point. This is an issue because the user can still scan their IC card to login, but the login fails when the 'check status' screen is open (jp.co.ricoh.isdk.sdkservice.auth.custom.ui.SYS_RES_LOGIN intent returns false).

When our app is installed with 'SSO mode', our app in always in the foreground until the user is logged in. So when the 'check status' button is pressed, the status screen is opened, but not visible. Is there any way to prevent the check status screen from opening when our app is open? Or alternatively, is there a way to detect that the check status screen is open, so we can display a message to the user to close the 'check status' screen?

"""

The response I received from jverne suggested that the check status activity could be reset via the SDK. I did attempt this by setting the status to normal, as well as setting it to error and then normal. This did not have the desired effect. The login button is still missing until the 15 second timeout passes. Submitting a login request to the SDK fails during this 15 second period. Please advise how to overcome this failed login action.

We have completed the compatibility testing for ARC Document Solutions.

Could you please provide a production signature for the two attached files.