Log tool does not always include debug/verbose statements.
Incident Properties
Question
We log debug statements in out SOP application using
android.util.Log.d("nQ", "Logging message goes here")
However, sometimes I notice that when downloading devices logs (https://ricoh-ridp.com/ridp/faqs/how-do-i-collect-device-or-trace-logs) and analyzing with the LogCat tool (https://ricoh-ridp.com/logcat/lsp), the debug statements do not appear in the logs.
Sometimes I have had success with installing the developer tool, and make sure debug/verbose logs resolve the problem, but not every time.
Is there a setting in SP mode we can update, or a setting anywhere else in the SDK?
Thanks.
Request for FAR SDK documentation
Incident Properties
Question
Hi Team,
When FAR is enabled on the device along with our Embedded application we are setting the authentication method to Custom.
Which is not allowing the AD user to login to the device as an administrator.
We would like to have the FAR SDK documentation in order to enable the AD users to login as administrator to the device. Please share the documentation as soon as possible.
Thanks,
Vikas Goud
MAINTENANCE SIGNATURE FOR SMARTSHARE V1.1.12
Incident Properties
Question
Hi,
We would like to ask for a maintenance signature for SmartShare Android embedded solution.
- Exception details at the time of remote configuration;
Best regards,
Anderson Palhano.
Cancel the Jobs which have not been accepted such as pending in the print spooler
Incident Properties
Question
Hi Ricoh Team,
In the Ricoh Unified Client Application, we would like to purge the processing/pending printer jobs when a user logs in to the device.
In order to implement this feature, after user successfully logs in, we are calling the following API to cancel all printer jobs.
Cancel all printer jobs (PUT) - /rws/service/printer/jobs
Sample Code:
public static void cancelAllPrintJobs(String deviceUsername, String deviceUserPassword, String deviceProductId, ILog log) throws URISyntaxException, IOException {
log.d(String.format("cancelAllPrintJobs deviceProductId: %s", deviceProductId));
DefaultHttpClient client = new DefaultHttpClient();
URI uri = new URI(String.format("%s://%s:%s%s", RicohSDKConstant.DEFAULT_SCHEME, RicohSDKConstant.DEFAULT_HOST_NAME,
RicohSDKConstant.DEFAULT_HTTP_PORT, RicohSDKConstant.REST_PATH_CANCEL_ALL_PRINT_JOBS));
HttpPut request = new HttpPut(uri);
request.addHeader(new BasicHeader("Host", String.format("%s:%s", RicohSDKConstant.DEFAULT_HOST_NAME, RicohSDKConstant.DEFAULT_HTTP_PORT)));
request.addHeader(new BasicHeader("X-Application-Id", deviceProductId));
request.addHeader(new BasicHeader("Content-Type", "application/json; charset=utf-8"));
String auth = deviceUsername + ":" + deviceUserPassword; // SDK format with an empty pw
String oneShotAuthorization = "Basic " + Base64.encode(auth);
request.addHeader(new BasicHeader("X-SS-OneShotAuthorization", oneShotAuthorization));
StringEntity entityPut = new StringEntity(String.format("{\"jobStatus\":\"canceled\"}"));
request.setEntity(entityPut);
HttpResponse response = client.execute(request);
int status = response.getStatusLine().getStatusCode();
log.i(String.format("cancelAllPrintJobs by auth[%s], Status: %s, response[%s]", auth, status, EntityUtils.toString(response.getEntity())));
}
This API is not working as expected when there are large number of documents having more pages,
For Example:
1. A user is logged into the application and given a print of two documents having a size of 75 pages each.
2. The First document is accepted by the device and visible in the print queue and starts printing, when the printing is continuing the user logs out due to timeout.
3. At that time when the different user logs in again, I wanted to cancel the two jobs but if I call the above API, the first job appearing on the device changes to cancelling state (taking quite some time to complete cancellation).
4. After the First Job is cancelled successfully. the second Job is accepted by the device and appearing on the device and starts printing but I wanted to cancel the first and second Jobs at the time of login.
I read the following in the documentation and assuming the second Job which is not accepted by the device is in the print spooler pending state.
Could you please confirm is it possible to cancel the Job which is pending in the print spooler (not accepted by the device)? If so, could you please provide us the details to cancel the Job or else we can consider it as a device limitation and convey the same to our Product management team.
Common Information > WebAPI Specifications > Printer > 02. Printer Job (Start of New Job/Obtain Information List > overview
Device Details:
Thanks & Regards,
V R V Madan
Copy Function Request
Incident Properties
Question
Hello Team,
We are trying to get all Copy functions in our app.
Instead of creating the UI, Is it possible to use the native copy app from our app?
Also we need to share the statistics once the copy function is done.
Production sign SLNX 24R1 Dm agent
Incident Properties
Question
product sign
Maintenance signature request for PaperCut MF v3.2.6
Incident Properties
Question
Hi,
Please find attached version 3.2.6 of the Papercut MF application for a maintenance signature.
The changes are described as follows:
-
Fixed an issue where switching between languages didn't work on certain models
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,
NYP failed login attempts
Incident Properties
Question
We have a customer that has multiple Ricoh printers and is using our embedded app to log into the printer. We are sending the user credentials to the printer through the jp.co.ricoh.isdk.sdkservice.auth.custom.ui.REQ_LOGIN broadcast intent. This works on all of their printers accept one that they have that is an IM C4500. The login response result returns false every time. I looked at the Login Response object in the sdk and it's looks like it only returns that boolean value, and not the reason why the login failed. Is there any additional logging around the result that we can capture to see why the login keeps failing, or are there specific settings on the printer that would block a login?
Can device cancel copy job during logging out if no paper?
Incident Properties
Question
Question:
Can device cancel copy job during logging out if no paper occurred?
We tested the device behavior with IM C4510 and IM C3500 (refer to the attached firmware info) by following the steps as below:
- Log into device with custom authentication.
- Open Copy app and start Copy.
- When printing is going on for the copy job, no more paper in the tray and the job stops. The device screen prompts the message to ask user to load paper on the tray.
- User logs out from device, but device does not cancel the copy job.
As a comparison, we tested on both devices and had a check of the device behavior with paper jam, but device does cancel the copy job when user is logged out:
- Log into device with custom authentication.
- Open Copy app and start Copy.
- When copying is in progress, paper jam occurs due to paper misfeeding.
- User logs out from device, and device does cancel the copy job, refer to the below copy job event:
05-09 10:20:11.402 1535 1535 D PrintixGo:TrkRvr: handle: COPY ACTION EVENT detected: {"data":{"jobId":"1k3tpw7snc77","jobNumber":103,"jobStatus":"canceled","restrictionPanelId":["7"],"restrictionPanelIdInfo":["personal_authentication"],"copies":1,"scanningInfo":{"jobStatus":"canceled","scannedCount":3,"resetOriginalCount":0,"scannedSheetCount":3,"selectedTray":"tray1","modifiableOriginalSizeMixed":false,"cmbDpxState":"duplex"},"printingInfo":{"jobStatus":"canceled","printedCopies":0,"trayInUse":""},"defactoJobEnd":false,"notBeChangedKey":["printColor"],"logoutPossible":true,"eventDetail":"other"},"id":"copy:74","subscriptionId":"C000004","date":"2024-05-09T14:20:10.960Z","event":"job_event"}
Why the copy job can be cancelled during logging out if paper jam occurred? Is that possible device also cancels the copy job during logging out if no paper occurred (for example, by configuring any SP mode setting)?
Thank you.