Skip to main content
Solved

Double purchase sheet on first purchase

  • 30 November 2021
  • 1 reply
  • 209 views

Forum|alt.badge.img+2

Hello,

 

I am testing my purchases with a test user and when I do my very first purchase I get presented with two purchase sheet from apple. After I enter the password to confirm the purchase on the first one, a second purchase sheet is shown after. Then I re enter the password a second time an I am able to do the purchase. This happens only on the very first purchase, the following purchases do not show this behaviour.

 

Here’s my traces:

2021-11-30 08:47:05.098181+0100 StickerTune[569:24807] [Purchases] - DEBUG: ℹ️ makePurchase
2021-11-30 08:47:05.100231+0100 StickerTune[569:24807] [Purchases] - DEBUG: 💰 Purchasing product from package  - st_499_1m in Offering st_monthly_yearly
2021-11-30 08:47:05.110488+0100 StickerTune[569:24807] [Purchases] - DEBUG: ℹ️ PaymentQueue updatedTransaction: st_499_1m (null) ((null)) (null) - 0
2021-11-30 08:47:21.310017+0100 StickerTune[569:24807] [Purchases] - DEBUG: ℹ️ applicationDidBecomeActive
2021-11-30 08:47:22.494746+0100 StickerTune[569:25165] [tcp] tcp_output [C1.1:3] flags=[R.] seq=359701540, ack=2894476465, win=2047 state=CLOSED rcv_nxt=2894476465, snd_una=359701463
2021-11-30 08:47:38.795250+0100 StickerTune[569:24807] [Purchases] - DEBUG: ℹ️ applicationDidBecomeActive
2021-11-30 08:47:43.676144+0100 StickerTune[569:24807] [Purchases] - DEBUG: ℹ️ PaymentQueue updatedTransaction: st_499_1m 1000000920701796 ((null)) (null) - 1
2021-11-30 08:47:43.680226+0100 StickerTune[569:24807] [Purchases] - DEBUG: ℹ️ Loaded receipt from url file:///private/var/mobile/Containers/Data/Application/F60D1DC2-8F59-4134-8E09-516C52DE15A1/StoreKit/sandboxReceipt
2021-11-30 08:47:43.680426+0100 StickerTune[569:24807] [Purchases] - DEBUG: ℹ️ Found 0 unsynced attributes for App User ID: $RCAnonymousID:d9553d3dd15e4aec9f5eecda5d06869e
2021-11-30 08:47:43.682637+0100 StickerTune[569:24807] [Purchases] - DEBUG: ℹ️ There are no requests currently running, starting request POST /receipts
2021-11-30 08:47:43.682729+0100 StickerTune[569:24807] [Purchases] - DEBUG: ℹ️ API request started: POST /v1/receipts
2021-11-30 08:47:43.902555+0100 StickerTune[569:24807] [Purchases] - DEBUG: ℹ️ applicationDidBecomeActive
2021-11-30 08:47:44.990300+0100 StickerTune[569:25606] [Purchases] - DEBUG: ℹ️ API request completed with status: POST /v1/receipts 200
2021-11-30 08:47:44.996460+0100 StickerTune[569:25606] [Purchases] - DEBUG: ℹ️ Serial request done: POST /receipts, 0 requests left in the queue
2021-11-30 08:47:44.999024+0100 StickerTune[569:24807] [Purchases] - DEBUG: 💰 Finishing transaction st_499_1m 1000000920701796 ((null))
2021-11-30 08:47:45.001321+0100 StickerTune[569:24807] [Purchases] - DEBUG: ℹ️ Vending PurchaserInfo from cache.
2021-11-30 08:47:45.554296+0100 StickerTune[569:24807] [Purchases] - DEBUG: ℹ️ PaymentQueue removedTransaction: st_499_1m 1000000920701796 ((null) (null)) (null) - 1
2021-11-30 08:48:15.087654+0100 StickerTune[569:25948] [tcp] tcp_input [C4.1:3] flags=[R] seq=2954479620, ack=0, win=0 state=LAST_ACK rcv_nxt=2954479621, snd_una=318890755
2021-11-30 08:48:15.088228+0100 StickerTune[569:25948] [tcp] tcp_input [C4.1:3] flags=[R] seq=2954479621, ack=0, win=0 state=LAST_ACK rcv_nxt=2954479621, snd_una=318890755

Is this the expected behaviour for the first very purchase done with the sdk?

 

Thanks in advance,

Libero

Best answer by tina

Hey @libe 

This is actually an Apple sandbox quirk. Other developers and myself have also experienced seeing the payment sheet twice (sometimes even more) when performing a test purchase. Nothing to worry about here! The production environment once you ship your app is much more stable.

View original
Did this post help you find an answer to your question?

1 reply

tina
RevenueCat Staff
Forum|alt.badge.img+10
  • RevenueCat Staff
  • 338 replies
  • Answer
  • December 8, 2021

Hey @libe 

This is actually an Apple sandbox quirk. Other developers and myself have also experienced seeing the payment sheet twice (sometimes even more) when performing a test purchase. Nothing to worry about here! The production environment once you ship your app is much more stable.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings