SDK/J

Hello

I removed all dev keys on the SDK/J application KofaxRicohClient when building it.

After then, I requested a demo version automatic on the RiDP portal and I can deploy success the app on a Ricoh device.

But when starting up the app via WIM, it shows error J501, and Rlog log125 says the problem relates signed key with SHA-1.

- How do I fix this this issue in SDK/J app to request correct demo versions in the future?

- Please help to make a demo signature for the attached version

Thank you very much

Ngoc

Hello,

Is IPv6 supported on the SDK/J platform? More specifically, should it be possible to:

- Make calls from our application to a server using an IPv6 address?

- Assign an IPv6 address to an SDK/J MFP and deploy to that MFP using RXOP and an IPv6 address?

If yes, on what versions of the SDK/J platform is it supported?

Thanks,

Peter

Per Joe's request opening a ticket.

I made a minor change to the solution and rebuilt it using the same tools we've always used. The .ZIP file created fails to install using our installer with the message "Error: 0." When I try to install it through the WiM, I get the error message "The extended feature file may be altered." 

If I go back to 1.5.8 I get the same error. When I go back to 1.5.7 (our dev signed release not the production signed release) it installs properly.

Seemingly something else has changed in the environment. I think the error message may lend a clue. Can you tell me under what cicrumstances the MFP rejects a ZIp file with the message "The extended feature file may be altered."?

Seems like a checksum or something similar.

Thanks,

Nick.

We're running into and issue where our application is having trouble detecting the EECU on a couple of specific models. We've got them to update the the devices to the newest firmware and we've double checked that the settings are correct. We've tested the same build on other devices and we don't see the same issue.

The device giving us issues is a C6503 running Java version 12.59.01. Is there anything with that model or that Java version that would cause the EECU to behave differently than any other device?

A customer recently found a minor bug with numebr formatting causing our application to crash. We've fixed the issue and would like a maintenance signature on the build.

Hello,
 

Please find attached version 6.0.7 of the PaperCut SDK/J application. It fixes the following issues:

- Fixed an issue that prevents the embedded application connecting via the binary-rpc server port (instead of the SSL port) if the JRE does not support the SSL protocol specified in the embedded application

The application supports SDK 4/5/7/10/11/12 on uWVGA, WVGA and SVGA.

Note: I have modified the Client.dalp file to have our production product ID instead of our development product ID and I have also removed the development signature from `pc-ricoh-client.jar`.

Regards,
Daniel

Hi, When we certified Ricoh for Beacon we obtained an ACL file for SP mode settings we wanted to set remotely. We have a new setting we want to add and need to generate a new ACL. I thought there was a menu item specifically for ACL generation but I could not find it. I also looked through our archived incidents for a request for ACL and didn't find that either. Can you please point me in the right direction for creating the ACL file?

Thanks,

Nick.

Hello,

We have had a customer that has reported the following odd behaviour only when the MFD wakes up from energy saver mode.

• When our embedded application tries and authenticates a provided set of admin credentials the MFD's API returns error code "1" (jp.co.ricoh.dip.devicemanagement.DeviceManagementException.ERROR_CODE_SYSTEM_ERROR).
  
  One example of this occuring in the attached 125 log is 2018-12-05 12:22:22,269 ERROR DeviceManagementUtils - Device management exception, code=1 (System error) [EventManager Thread:java.lang.ThreadGroup[name=PaperCut,maxpri=10]]
  
  This is the below Java code that produces the error:
  DeviceManagementService dmService = jp.co.ricoh.dip.devicemanagement.DeviceManagementService.createLocal(productId);
  jp.co.ricoh.dip.devicemanagement.LocalDirectory dir = dmService.getLocalDirectory()
   
• When our embedded attempts to invoke `com.sun.net.ssl.SSLContext.getInstance("TLS")` it throws a NoSuchAlgorithmException
  This can be seen in the logs multiple times but one example is:
  2018-12-05 12:22:25,097 DEBUG SslHelper - Unable to configure HTTPS [startup-1544030544875].
   

Upon rebooting the MFD all this function calls work correctly, it is only when the device goes to sleep and resumes from sleep the above behaviour can be seen. The customer reported this issue persists until a reboot is performed so it is not just a once off happening immediately after resume from sleep. I have attached the RLOG files. The SDK/J version reported by our application is 10.27.

The devices are various models (unspecified) by they are all 2002/2003 models.

I am trying to add support for Elatec card readers.  I currently am able to use RFIdeas card readers.  To grab the RFIdea I used the CardReader example in the source material.  It works great for RFIdea card readers on all printers.  I have 2 printers to test on.  MPC 305 SPF(platform 10.xx) and MPC 306 SPF (Platform 12.xx Android gen 2).  When I connect the Elatec card reader to my 305 it works, I am able to get the connected USB event and tie into the card reader.  When I connect the Elatec card reader to my 306 I do not get any event that the card reader has been plugged in.  The strange thing is the 305 does send the event and works.

In order for me to get any card reader to work I have to plug into the back usb ports.  I am wondering if the printer itself grabs hold of the elatec reader and handles it before my application can. 

I did notice that with the Elatec card reader plugged into the back of the card reader the printer will wake from standby if a badge is scanned but I don't see any reference to the scan in the rsh logs. 

Any help would be appreciated.

Thanks,

Casey