by Mike Ricotta - December 9, 2021
A required update of the ArcanePOS mobile application has been released to iOS and Android. Please be sure to review the information below for a better understanding of what has changed and what to expect.
Heck Yes! This version includes the Stripe SDK v2 which supports use of Stripe’s new M2 reader.
ATTENTION: This version contains a security patch released in Nov 2021 which is required for all BBPOS Chipper devices. After you download the updated application, you must run the firmware updates on each of your BBPOS Chipper readers. This is required and will automatically run upon connecting to your device. Before beginning the process, be sure to charge your device fully and do not close the app nor turn off the device during the upload process. To complete the upload process, visit “Discover Readers” on the mobile app, perform the discover readers search, then select your reader to connect to it. During the connection process, the firmware will upload to your device automatically, this may take 5+ minutes to complete (again, do not close/power-off the app/device). During this process your reader will flash blue and green, yellow, or white lights for several minutes. Prior to completion, the flashing light will change to an orange or red signal and all of blue leds atop your device will light up. Immediately upon completion, the device will return to its normal state (blue light) and the mobile application screen will change to indicate that the reader has been connected.
As indicated above, this version includes the Stripe SDK V2 which is required for Stripe’s 2022 enforced account changes including location assignment for all readers. While the V2 SDK has been public for some time, the open source community had not released a ReactNative Stripe SDK V2 wrapper for iOS and Android SDKs, so we’ve taken it upon ourselves to complete that and release that within this update.
Stripe now requires all devices to be assigned to a location. As such, the SDK V2 update also attaches a location to each reader when the reader is being registered. If no location exists, a default location is created. The default location creation step was released in an earlier version of our app. Future roadmap changes will include reader management.
In order to address priority needs for current existing users of our application, barcode scanning will be pushed into late Q1 in order to accommodate these ’21 Q4 and ’22 Q1 changes: