#tyrzaphir_code

1 messages · Page 1 of 1 (latest)

cyan willowBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1326294641452253248

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

tall tartan
#

Here's an image of the screen I am referring to

IMG_6547.jpg
valid hollow
#

Hmm as far as I know, this screen is built in to the SDK. You shouldn't need to write custom code to get these buttons to work

#

Are you seeing any errors or logs in your logcat when you click on these?

tall tartan
#

I'll try adding setEnableCustomerCancellation in a bit. Here's the logs

📎 message.txt
#

And here’s a video showing the button doing nothing when pressed

valid hollow
#

The button did take you back to your app, yeah?

#

Seems a tad bit slow but seems to be working

tall tartan
#

Here is a video of me not pressing the button. It seems like it goes back to my app after 3-5 seconds, regardless of whether the button is pressed or not

#

And I tried setting EnableCustomerCancellation(true) and I saw no change in the behavior. I have noticed the "waiting for payment" screen shows an X in the top left corner for the user to cancel the payment before tapping a card regardless of the EnableCustomerCancellation setting.

valid hollow
#

Hmm that is indeed interesting. I'd recommend writing in via support so that we can escalate this to the correct team to look into this -
https://support.stripe.com/?contact=true

Stripe: Help & Support

Find help and support for Stripe. Our support site provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.

tall tartan
#

Will do, thanks for your help

#

I have some additional questions around the review process and the discord bot told me to use this existing thread:

  • For security reasons, we only allow devices to communicate with our server that have been approved by an admin. Whenever one of our apps communicates with one of our servers, it sends its unique device ID along with the request (from Settings.Secure.getString(contentResolver, Settings.Secure.ANDROID_ID). If the server recognizes that device ID because an admin had entered that ID into the database in the past, the request is fulfilled. If the device ID is not recognized, it logs an error and rejects the request. We submitted an early version of our app for review yesterday, and it was rejected because "We were unable to install and launch your app. After Loading Screen by launching App, Errors message was showing and failed to launch application." In order for Stripe to properly test and review our app, we will need to know the device IDs of the test devices ahead of time to enter into our system. If I enter the device ID used for yesterday's review (pulled from the logs), will that work for all future reviews?

  • When we first tried uploading an APK for review, I got an error saying that our APK requested a forbidden permission "REORDER_TASKS." Searching in android studio pointed us at only one place this was referenced: the line <uses-permission android:name="android.permission.REORDER_TASKS" /> in /.../.gradle/caches/8.9/transforms/720a7237bde242f065ee3f884c907714/transformed/core-1.6.1/androidmanifest.xml. We removed that line, recompiled the apk, and then were able to upload the APK for review successfully. However, it seems strange that we need to make an edit to the gradle installation every time we go to submit an APK for review. Is there some other way we should be removing the request for that permission?

valid hollow
#

Unfortunately my team doesn't know anything about the review process.. You can add these questions along with the issue you're reporting in the same ticket. Support will put you in touch with the right team that can answer these