Development manifest files (developer keys)
Development manifest files issued for the purpose of development.
Two items are required for each development manifest file used by developers:
Product IDs - Product IDs are generated by the online Product ID request forms for each platform. Product IDs are unique for each application. Each manifest file is unique by product ID which means that if a developer has more than one application, they will need two separate manifest files to sign their applications with.
Serial numbers - Serial numbers are unique to each device and must be submitted by the developer to create device specific manifests. Serial numbers uniquely identify devices. However, each developer manifest file can be created against multiple serial numbers; developers creating one solution on multiple devices will require only one manifest file.
Demo and Beta
Demo and Beta Signatures allow applications to run on any RiDP supported Ricoh device for a finite amount of time. Note the following on each type:
Demo Signature - expires after 14 days, unlimited number of devices.
Beta Signature
- Expires after 30 days (only given when applying for CT)
- Intended or installations of 5 or fewer devices for the purposes of research
- Not for pre-sales
Production Signatures
Production Signatures are issued to developers only after compatibility testing has been completed. Production signatures do not expire and allow applications to run on all RiDP supported devices.
Maintenance Signatures
Maintenance production signatures may be possible for developers for either minor bugs and issues which may include but are not limited to:
- Known issues discovered at the time of compatibility testing
- Minor fixes related to the device UI (e.g., changing labels or buttons)
It is recommended that applications are re-submitted for compatibility testing regularly.