I’m Square Dev AI, here to help answer your question!
Based on the information you’ve provided, the following documentation will help answer your question:
If this documentation helped you find a solution, please check the box indicating that this reply solves the problem.
Otherwise one of our Developer Advocates will provide additional assistance shortly.
The error code “checkout_microphone_permission_denied” indicates that the application doesn’t have the necessary permissions to access the microphone on the device. This is required for the Square Reader SDK to process card payments using the magstripe reader, which connects via the headphone jack and uses the microphone input for data transfer.
Even though you’ve confirmed that microphone permissions are enabled for the app on the device, the error suggests that the app is still not able to access the microphone. This could be due to various reasons such as other apps using the microphone at the same time, or device-specific restrictions.
You should ensure that no other apps are using the microphone when a payment is being processed. Also, check if there are any additional settings on the device that could be preventing the app from accessing the microphone. If the issue persists, you might need to debug the app on the device to get more detailed information about the error.
So this doesn’t really narrow anything down. Can you not offer any troubleshooting advice on this? I can’t tell my users to check if they have other apps that use the microphone at the same time. This cannot be a realistic expectation for a developer to troubleshoot.
This is exclusively iOS. And they have tried deleting and reinstalling the app. This isn’t affecting all users. Just a select, primarily new set of users. Previous users have reported it only for the issue to go away of its own accord after a few weeks.
Do you have any updates on this? Users are saying they can pair the reader via iOS bluetooth screen. But cannot pair the device via the Square Reader SDK screen. It simply stalls with no result.
I’m also seeing that there’s uptime issues with the Square POS API? Are these related?
Let me guess: Square has no intent of patching this issue.
By the way, we figured out the fix. And it had nothing to do with the error message. You had to download Square POS, pair it via a device code. Then repair the card reader with our custom POS before it worked…
None of this is documented. Is there no one working on documentation anymore?