SmartSDK

We are requesting a new maintenance signing request.

This update includes multiple bug fixes and optimizations including

* Issues with rfideas readers where a user would sometimes have to swipe a badge twice to log in.

* Simplification of connection tests and fixing network socket connection leaks

* Caching the dalp file. Open the dalp file once and cache the contents instead of opening it each time a setting is pulled

* Improved login flow.  Removed long poller and use a javscript bridge with the auth server to handle logging into the printer in SSO mode.

* detect network drop and retry connection as soon as network is back online.

Request for maintenance signature, bug fixes and other enhancements.

We are planning to change our product version from 1.3.0.594 to the format <GA YEAR>.<QUARTER>.<BUILD#>.e.g. 2025.2.100

GA Year value will be four digit year value.

Would like to know if there is any restriction from Ricoh in using the GA Year for Major version? Please let us know if there is any restriction and is it ok to use the GA Year as the major version value or not?

Request for maintenance signature, bug fixes and other enhancements.

This is essentially the same question/request made in Incident ID#: 4019.

Shell is requesting the authenticated username field on the MFD be increased to be larger than 32 bytes.

Anthony Mare is the Ricoh contact on the call that requested we do this.

The customer considers this a high priority issue.

Regards
Bryan

We are running into another issue where we are running out of file descriptors when making connections on an MP5055. This issue we found when doing some stress testing with badging.  When we swipe a badge we collect the data and then send it to our authentication server over https.  After a certain number of card swipes we start getting the "Too may open files"  error when trying to connect.  We verified that we are closing the connection each time, but something on the printer still seems to be holding on to it.  Is there anything with the 5055 or android 17 which may still hold on to socket connections?

Hi, 

We would like to ask for a maintenance signature for Smartshare Android embedded solution.

•  Handling error messages;

Best regards

Anderson Palhano

Hi

A function of Tungsten KTA product, our RegistrationTool is using RXOP-3.8.9.

The Whitesource scan tool shows a report about security vulnerability with the lib: RXOP-3.8.9-release\lib\dep-libs\bcprov-jdk18on-176.jar.  The risk is identified here: https://www.mend.io/vulnerability-database/CVE-2024-29857

Question:

- Can we replace this lib to newer version for RegistrationTool app?

- Do RiDP have any plan upgrading this lib in the next RXOP release?

Kind Regards

Ngoc

Dear RIDP:

As discussed in the attached Email thread with Diane Jiang from RIDP, Tungsten Automation would like to submit for certification Tungsten Printix Go 2.4.0.13 and Capture 2.4.0.5.

The application was previously certified by EMEA RIDP and release notes of the changes since last certification are attached.

Product ID's: 1667825665/1667825666

The application supports G2, G2.5 and G3 devices.

Outside server connection: https://api.devenv.us.printix.net (firewall should be configured to allow *.printix.net)

Please product sign dm agent 1.3.1 for 4neo