You are here:
Migrating to Point of Sale Release App
Migrate from the UAT app to the Point of Sale (POS) Release app. Confirm that you have received a TestFlight invite to access the new app.
Access Your Test Flight Invite
- Search for the TestFlight email invitation to the Release app. The email label reads, "Salesforce INC has invited you to test POS."
- Select View in TestFlight to view your redeem code. Save this code as you need it to download the Release app.
Release App Download and Setup
- Open the currently used PS POS app on your device.
- Sync any offline activity or pending orders, if applicable.
- Exit the app and go to the home screen of your device. Then, delete the app from your device. For customers using MDM, use it to delete the UAT-specific app and push the new TestFlight invite to the UAT devices.
- Open the TestFlight app and go to the PS POS app entry details by scrolling to the bottom. Select to remove the PS POS app entry from TestFlight.
- The screen asks you to redeem a code to download the Release app. Tap .
- Enter your code which was listed in your TestFlight invite email
-
After successful redemption, the app refreshes again and you can access the new Release
app. TestFlight labels the app as POS for the release app, but the app icon
appears as PS POS.
- Exit this app, tap the newly-download PS POS app on your home screen, and scan the QR code in the CMS (). Confirm thatyou've granted camera permissions to this new app in your iOS settings.
-
Enter an app token or select the default app.
-
On the next next screen, rapidly tap the upper right corner 6–7 times. This displays a
window that has your new installation ID. Save this ID and follow the steps in this article to register
the new device in CMS. If the register isn't activated in CMS, the app displays the ID on the
Welcome to Register screen.
- After successful registration, return to the PS POS app and log in. Proceed with testing as usual.
Frequently Asked Questions (FAQs)
Address common questions about POS App migration, including email notifications, testing app versions, and handling old builds.
Does migration trigger any email notifications besides the invitation to accept the Retail Cloud Release app developer account?
The only additional email triggered by migration is the new TestFlight invite from the Point of Sale Release developer account.
If the change for app version 10.9.1 is made after I’ve started testing, how will that affect me testing 10.9.1?
Starting with app version 10.8.1, this is the only TestFlight version available for UAT. We won’t send UAT-specific app TestFlight invites for a version after we begin inviting merchants to the release app TestFlight.
What happens to old builds post-migration?
Old builds remain on devices until manually deleted. See step #3 in this section for instructions on how to delete old builds during migration.
Do I use a new version? For example, if I am on version 9.8.1, do I only test the latest version after migration?
Yes, if you are testing version 10.8.1 or later, use the Release TestFlight. As this is not a rolling update, both apps aren’t available on TestFlight at the same time. TestFlight builds are only available for 90 days, so you can’t test version 9.8.1 anymore.
What if I need an older release version for testing?
If you require a version 10.7.1 or earlier, the app team generates a new build within the current release cycle. The new version number will match the upcoming release version, while the build number retains the requested TestFlight version and build number. For example, if you request 10.7.1 26688 during the 10.8.1 release cycle, the new TestFlight entry has Version: 10.8.1 and Build: 10.7.1.26688. If the same request is made again after 90 days during the 10.11.1 release cycle, the updated entry has Version: 10.11.1 and Build: 10.7.1.26688.
For versions 10.8.1 or newer, if the build is still available on TestFlight, no action is needed, as TestFlight builds remain accessible for 90 days. However, if the build has expired, the app team generates a new build using the same versioning and build number scheme applied to 10.7.1 or earlier builds.
