SmartSDK

Hi team,

I'm trying to get a better understanding of how the Print SDK works in respect to PDLs.

I'm testing pull print on Ricoh MP C307 (Generation 2) device.

First I send a Web API request to get supported PDLs. The SDK gives me this:

Supported PDL is:
{ "pdl": ["pdf", "pcl", "ps", "tiff"] }

then I send the print SDK request for the post script file.

{ "filePath": "http://example.com/file.ps", "pdl" : "ps" }

The response is HTTP 400 error:

HTTP Status 400: Bad Request
{ "error": [{ "message_id": "error.exclusive_job_settings", "message": "filePath_pdl"}]}

Looking at the error code on SDK it says:

I tried with pcl and tiff file and got the same result.

The only PDL that works is pdf.

I performed the same test on generation 3 device, Ricoh IM 2010 and it worked on all of the supported PDLs.

I wonder if you could help us and tell us what is the issue and what are we missing in here?

We have a custom authentication Android application running on RICOH SOP v2.5 devices. This application has undergone compatibility testing, and we have obtained product signatures that do not have an expiry date as mentioned in the ridp portal.

Currently, we are facing an issue with the X-SS-AccessToken used for calling SmartSDK APIs from a remote application. The error we receive is:

{"errors":[{"message_id":"error.invalid_header_value","message":"X-SS-AccessToken"}]}

Following are the APIs which are being used by us:
/rws/status/system (GET) — Device status
/rws/property/deviceinfo (GET) — Device model info
/rws/property/smartSdkInfo (GET) — Device SDK info
/rws/sop/webbrowsernx/shortcuts (POST) — Register listing application
/rws/property/usbDeviceList?number=1-2-3-4-5-6-7-8-9-10 (GET) — Get the list of registered USB devices
/rws/property/usbDeviceList

Request for generating a new production token for remote application

Token type : Production
Product ID: 1711276315
Vendor Name: OpenText
Application Type: Remote Application
Application Name: Secure Access for Ricoh
Expiration date : 20351112
MFP Serial number(s): NA as this is for production

Partner Key(Public) has been attached to the incident with name "Publickey.pem"
Attaching the compatibility test report for reference.
 

To the Technical Support Team,

We are encountering a critical connectivity issue with our embedded Android application running on a Ricoh 501 printer. When attempting to access the application (package br.com.smartshare), the operation fails with an SSL error.

Device Information:

• Model: Ricoh 501
• Issue: Application fails to connect to the server.

Error Details:The error message displayed on the screen is:"Falha ao conectar: SSL handshake aborted: ssl=0x5200ab30: I/O error during system call, Connection reset by peer"

Log Analysis:Attached is the full system log (LOG_202511240921.txt). Upon analyzing the logs, we identified the following critical exception occurring at timestamp 09:19:37.889:

 

E #### SS:RC:[CLI_HTTP_SERV] - : javax.net.ssl.SSLException: SSL handshake aborted: ssl=0x5200ab30: I/O error during system call, Connection reset by peer at org.apache.harmony.xnet.provider.jsse.NativeCrypto.SSL_do_handshake(Native Method)

 

 

 

Additionally, the logs show multiple NoClassDefFoundError warnings related to java.time and java.util.Optional classes (e.g., timestamps around 08:58:20), which suggests the embedded Android version might be outdated or lacking necessary libraries for modern TLS handshakes.

Hypothesis:It appears the device is attempting to establish a secure connection using an outdated TLS protocol (e.g., TLS 1.0 or 1.1) or an unsupported Cipher Suite, causing the server to reset the connection (Peer Reset) immediately during the handshake.

Request:

1. Could you verify the supported TLS versions on this specific firmware/Android version?
2. Is there a firmware update available that enables TLS 1.2 support for embedded applications?
3. Please advise on how to resolve this SSL Handshake compatibility issue.

Attached you will find the screenshot of the error and the complete log file.

Hi Team,

I am writing to inquire about the future of the classic apps on Ricoh devices (Printer, Scanner, Copier).

Are there currently any plans to deprecate these applications, or will Ricoh continue to support them?

Is it possible to disable or otherwise intercept the home button press on the device? We have a workflow that we would like to enforce in our application after the point of user login, however the home button would skip this workflow. Whilst the user's device session would behave just fine, this could result in native jobs being tracked improperly against users on the server.

If we were able to disable the home button whilst inside the app, or intercept the home button press and prevent it from pausing our app, we can ensure the workflow is followed. Is this possible?

Do you have any suggestions or best practices to reduce the size of our APK?  Most of our issue is the /lib folder.  Is there a standard or any recommendation to reduce the APK size?  Or, are there known issues when trying to reduce the APK size that could cause an issue with the Ricoh install? 
Thanks!

Kelly

Hi team,

This request serves as an advance notification regarding our plan to submit a request for a maintenance certificate in early December (within the first two weeks).

We are finalising development on a feature that integrates support for printing using Pull Print SmartSDK API. The current certified version is 2.0.4, and the version for which we will be requesting certification is 2.1.0.

While we understand that early December often maintains normal business operations, we wanted to proactively inform you of our submission window to ensure our planned timing aligns smoothly with your internal review and processing schedules.

Please confirm that the first two weeks of December is an acceptable timeframe for the receipt and processing of this maintenance certificate request.

Thanks

Hi,
We are trying to add developement key for a new ricoh device.We can add the serial number and create keys but when we click on the download button it shows an error file not found.Attaching a screen shot below.  

We have started running into issues where customers are reporting issues when badging with our application on the newer

IMXX10 devices. So far the issue has been reported on an IM 2010, IM 2510, and IM 4510. The user swipes the badge but nothing happens.

When checking the machine logs we see  UsbService: reject requestDevicePermission for keystroke reader errors showing something else

is holding on to the card reader. We verified with the customer they were using the correct usb port and that IC Card Reader settings are 

set to Do Not use. Badging works on other Ricoh devices. Is there a new setting or something we need to configure for badging to work

on the newer models? I've attached the logcat files from one of the customers.