SmartSDK

Hi there, 

We run into a issue where Application authentication management settings for copier, printer, fax, scanner etc. are disabled at administrator tools section on printer, by which tracking did not logged user information with our Pharos sentry print application. When we manually enabled these settings, by this we could see the tracking got logged with user information. 

We would like to check this Application authentication management settings (please find the attachment for the screenshot of settings location on printer), is there any API or SDK method available which we could use pro-grammatically to enable these settings?

Thanks!

I'm running the sample web app in the Web Browser NX using the emulator.

I created an user in the AddressBook and I was able to successfully logged-in.

However, when I tried to get the user information through ricoh.dapi.auth.getAuthenticatorInfo(); I see only one field: "existsProvider": false

Am I missing setting anything in the emulator to get all the fields?

When I tried ricoh.dapi.auth.getAuthState I got the userId, userName and all the permissions.

Thanks,

Hi,

I am developing a scanning application. I put 200 pages in the ADF for scanning. My Application goes into the background when it scans around 60 pages. The scan continues in the background. When I click on the application icon, it resumes. How can I stop my application from going in the background? Kindly help.

Thanks.

Hi,

Please find attached version 1.1.11 of the Papercut Hive application for a maintenance signature.

The changes are described as follows

• Updated translations

• Redacted sensitive information from logs

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,

Papercut Team

I downloaded the RICOH SmartSDK Emulator 2.40 for MacOS.

The application takes more than 5 minutes to start showing this screen.

After it boots, it is extremely slow and hard to navigates.

Is there any way to enhance the performance?

Thanks.

Hello,

We are doing an implementation that uses the "/rws/udp/transmission" call, we noticed that when an administrator user is authenticated on the machine and this call is made, we are receiving an error code 403 {"errors":[{"message_id" :"error.not_authorized","message":""}]}.

This failure only occurs when an administrator user is authenticated, if it is a normal user it works normally.

Is there anything we can do to make this call work even with an authenticated administrator user? Or is this expected behavior?

Regards

Hello,

I was sent an issue from a customer where our custom authentication is unable to be displayed on the device. The device they are running is an IM C3010.

The deployment to the device works just fine. When a user goes to the device, our custom authentication is not displayed. In the device trace log, I see the following error:

07-10 16:50:22.921 4127 4127 E AndroidRuntime: FATAL EXCEPTION: main
07-10 16:50:22.921 4127 4127 E AndroidRuntime: Process: com.lrs.ricohapps.android.authentication, PID: 4127
07-10 16:50:22.921 4127 4127 E AndroidRuntime: java.lang.RuntimeException: Unable to start receiver com.lrs.ricohapps.android.authentication.framework.common.KeepAliveIntentReceiver: java.lang.IllegalStateException: Not allowed to start service Intent { cmp=com.lrs.ricohapps.android.authentication/.framework.common.AppKeepAliveService }: app is in background uid UidRecord{b06f09d u0a99 RCVR idle change:uncached procs:1 seq(0,0,0)}

This error is coming from a class provided in Ricoh's CustomAuth sample, which we based our authentication off of. The error appears to be coming from the KeepAliveIntentReceiver.java class when context.startService(pollingIntent) is called.

Looking this up online, I found the following:

https://stackoverflow.com/questions/46445265/android-8-0-java-lang-illegalstateexception-not-allowed-to-start-service-inten

This indicates I should call context.startForegroundService instead of context.startService if the Android system is O or later.

Another answer on that same thread indicates those shouldn't be used at all and the Android JobScheduler class should be used to keep the authentication alive.

I checked the latest smartSDK and it doesn't have any updates to the KeepAliveIntentReceiver class.

The question is, should either of these methods be used to try to alleviate this issue? Does RiDP recommend a different method to get around this?

We don't have a G3 device to test with here yet. So, would you have any idea why this works on G3 in your lab, but not on the customer's IM C3010? Maybe just an issue with this specific model?

I am also attaching the device tracelog from the date they reproduced the issue. If you search for the timestamps in the above exception message, you should be able to find the error.

Regards
Bryan

Hello,

Could you please let us know if IMC3010, IMC4510 and IMC6010 models are supported by our application.

Thanks

Please product sign dmext sop application