Blank "Square reader" screen after enabling bluetooth about react-native-square-reader-sdk HOT 8 CLOSED

@CharmisG Is there any update on this? This is undermining our ability to release the Android app which processes millions of Dollars in revenue. Does this need escalating to our Square account manager?

from react-native-square-reader-sdk.

@CharmisG Any update?

Has anyone else replicated this behavior on the latest version on an Android 12 device?

from react-native-square-reader-sdk.

That this is about Bluetooth permissions and Android 12 is telling; Google changed how those work as of that Android release. It's supposed to work for Reader SDK 1.7.1, but that's new. If you can play with the target SDK level, at API 30 or less the old permission rules should apply, which might avoid this issue.

from react-native-square-reader-sdk.

@fka3 I've tried building the quickstart app with targetSdkVersion set at 30 and result is the same. The screenshots are taken from the latest download of the quickstart app on an Android 12 device. Can you get it to run on an Android 12 device successfully?

from react-native-square-reader-sdk.

Well, dang it, it did when I cut that branch, but no, didn't just now. [Unprintable words here.]

Ok, back to API31 for me. You might check; there are two Bluetooth permissions that matter, but "dangerous" (per Google, because they imply location data) and needing user confirmation. If you can grant--- and I don't know enough React to know if this is possible---both BLUETOOTH_CONNECT and BLUETOOTH_SCAN outside of Reader SDK, that should at least avoid the issue.

But I'll try to figure out what went wrong (and how it worked for me at first!)

from react-native-square-reader-sdk.

No, actually, it does work for me; we just had the code with permissions set back to API 30's permissions.

Two questions:

1. When you say you "tried building the quickstart app with targetSdkVersion set at 30," what did you edit? If you only changed the target SDK, it probably should have failed to compile because of the new permission names... but you should have to edit both AndroidManifest to remove the new permissions, and also build.gradle to set the target SDK; did you adjust both?
2. Although I definitely suggest that we should explore with quickstart, the real target is your react app; is it possible to pull the final AndroidManifest from that? (Failing that, could you send me the .apk and I can pull it?). What I want to check is the targetSDK of the manifest and the permissions requested by it; they should be consistent. Either the targetSDK should be 30-or-less and the strings BLUETOOTH_CONNECT and BLUETOOTH_SCAN should not appear, or the target SDK should be 31-or-more and both should be requested.

Having realized that my test app was inconsistent, I'm now seeing working behavior targeting and running on 31/Android 12. I can do the test of targeting 30 while running on 31, if that's your target SDK?

from react-native-square-reader-sdk.

@fka3 @mormrod is this problem resolved? Should we close this issue now?

from react-native-square-reader-sdk.

I'd've liked the customer/developer to confirm, but yes, from what I observed, things work properly and the ticket can be closed. If @mormrod disagrees, we can reconsider.

from react-native-square-reader-sdk.