You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently use the Point of Sale SDK in our iOS app to complete sales and link the Square transaction id to our backend, saving the transaction details on our server. Occasionally our users want to go back to the linked transaction in the Square Point of Sale app to do actions such as refunds, reprinting receipts, etc. We have found that using UIApplication.shared.open(URL(string: "square-commerce-v1://")) will allow us to open the Square app, but it always shows the following error:
Is there some way to change the URL so that the error doesn't show up when trying to open the Square app? Or some other alternate method of directly calling the Square app to open without starting the sale? Ideally, for our use case, it would also navigate to the transactions screen, but simply opening the app without looking like it has broken would work as well.
The text was updated successfully, but these errors were encountered:
We currently use the Point of Sale SDK in our iOS app to complete sales and link the Square transaction id to our backend, saving the transaction details on our server. Occasionally our users want to go back to the linked transaction in the Square Point of Sale app to do actions such as refunds, reprinting receipts, etc. We have found that using
UIApplication.shared.open(URL(string: "square-commerce-v1://"))
will allow us to open the Square app, but it always shows the following error:Is there some way to change the URL so that the error doesn't show up when trying to open the Square app? Or some other alternate method of directly calling the Square app to open without starting the sale? Ideally, for our use case, it would also navigate to the transactions screen, but simply opening the app without looking like it has broken would work as well.
The text was updated successfully, but these errors were encountered: