Login is unavailable when 'check status' is pressed on screen
Incident Properties
Question
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?
Production sign Dm agent for 4neo
Incident Properties
Question
Please product sign the DM agent for 4neo
Restart Compatibility Testing
Incident Properties
Question
Ticket 5042 is for a compatibility testing request we had to cancel.
https://ricoh-ridp.com/ridp/support-system/incident/nqueue-billback-llc/1695919209/1017996890/5042
We are ready to start again, everything is the same, except for the build. Can we restart the testing process? How do we get you the new build?
List Product ID of Printix Go and PrintixCapture to my account for devkey generation
Incident Properties
Question
Relate to the incident ID#: 5127
Our Printix Solution uses 2 SmartSDK applications: PrintixGo (PID 1667825665) and PrintixCapture (PID 1667825666)
I can access to https://ricoh-ridp.com/forms/signatureservices/ricoh-smartsdk/development-keys, but Printix products do not list in my account.
I would like to add 2 product IDs to my product list at this tool.
- Printix Go (PID 1667825665)
- Printix Capture (PID 1667825666)
Purpose: We need to add new lab devices to the existing dev keys for 2 products above.
Thank you
Ngoc
SmartSDK Maintenance Signature
Incident Properties
Question
I have a fix for the next release of our SmartSDK solution that will require a maintenance signature.
1. We are still supporting devices containing a Smart Operation Panel with SmartSDK version 2.10 and later.
2. Authentication.zip is the only modified app.
3. The .dalp files are not modified.
Changes:
1. Fixed an issue related to off-prem authentication not parsing the XML response properly.
Regards
Bryan
[Update manifest-devenv.mf] Request Machine-SerialCode for new devices
Incident Properties
Question
Hi
We are using a manifest-devenv.mf file to develop PrintixGo client (product ID: 1667825665) but it is missing dev key (Machine-SerialCode) for new devices bellow.
We would get Machine-SerialCode for those Ricoh devices to update to our manifest-devenv.mf.
3099RC20002 | IM C2500(G2.5) |
9133R410261 | IM C2010 (3.0) |
9173R820031 | IM C4510 (3.0) |
4441R320132 | IM 4000 (2.5) |
3211X104217 | IM 600 (2.5 |
Thank you
Ngoc
Product sign the dm agent for SLNX
Incident Properties
Question
product sign the apk for dm agent slnx
Product sign the dm agent for SLNX
Incident Properties
Question
Please production sign the DM agent for slnx
Ricoh IM 460F and IM 370F (G3 device) with SmartSDK v4.00.00
Incident Properties
Question
Hi
Regarding this incident
01-11 10:44:22.339 4300 4300 I Inst:PkgInstSrv: FWUMODULEID=LUFMF1a_eplot
01-11 10:44:22.340 4300 4300 I Inst:PkgInstSrv: FWUPIECEMARK=D0DM5500E
01-11 10:44:22.340 4300 4300 I Inst:PkgInstSrv: FWUVERSION=1.06:06
01-11 11:56:44.220 3789 3789 I SdkServ : CMN:APP:GET_API_VERSION return 4.00.00
Unfortunately we in QTL don’t have access to FW that is not officially released (Exception: It is given to us for a specific test project).
So I’m afraid I can’t help you with your SDK issue.
...
Could you please advise for smartSDK version 5.0 on those models following the SmartSDK guide?
Maintenance signature for SmartShare v1.1.10
Incident Properties
Question
Hello,
We would like to ask for a maintenance signature for SmartShare Android embedded solution.
- Fixed bug in indexes of the document list.
Best regards,
Anderson Palhano.