#newtreyes
honest verge
twilit river
Do you have any specific questions here? It looks like the error message is fairly clear.
paper shadow
Hey, @twilit river . Thing is this same logic works without a problem on iOS and hanzo thought it should work just the same on Android
But it is not working and he wanted me to double check since I was already working on this.
twilit river
Can you link that thread?
paper shadow
Those 2
I think he never said it was going to work on Android
but then it would be strange to have it working on iOS but not on Android
feature parity would be missing in that case
twilit river
I might be missing something, but those conversations seem entirely unrelated
paper shadow
I can explain it all
So, I am working on implementing Tap to Pay both for iOS and Android.
on iOS @copper girder taught me that I could use the production reader (non simulated reader) as long as I used a test credit card like the one provided with the M2 Reader.
That worked like a charm.
Now, trying the same thing on Android gives me that error: E/StripeTerminal( 4865): com.stripe.stripeterminal.external.models.TerminalException: Debuggable applications are not supported in the production version of the localmobile reader. Please use a simulated version of the reader by setting DiscoveryConfiguration.isSimulated to true
This is the code on iOS
twilit river
Right, I understand the context and how we got here, I just don't understand the issue. You have to test on simulated readers when building with Android. That's different from iOS and totally expected as far as I can tell.
paper shadow
This is the code on Android:
So, on iOS you can test with the simulated readers or the real one.
On Android, you are limited to simulated readers only.
So there is no feature parity and expected, correct?
twilit river
Using the non-simulated, production version of the Tap to Pay reader with debuggable applications isn’t supported for security and compliance reasons. To test your integration with the Tap to Pay on Android reader, set DiscoveryConfiguration.isSimulated to true during reader discovery. You must set this value to false in the release version of your application.
With that in mind, you can test with non simulated version if you build a release version of the app that uses test mode API key.
