Hi,

I simulated to buy the pro version in TestFlight. When I installed the AppStore version my pro status was not reset properly.

Edit: This is how I found out, not part if the problem:

I recognized this, when I installed the App on the iPad and tried to restore the subscription: there was none.

  • steve228uk@lemmy.worldMEnglish
    5·
    1 year ago

    Hey, thank you!

    I really put some FAQs up about this.

    This was my first time working with in app purchases and it turns out apple doesn’t invalidate the receipt for testers unless you delete the app and re-install it. In hindsight I should have used two products: one for testing and another for production but at least I learnt something new haha

  • orangeNgreen@lemmy.worldEnglish
    2·
    1 year ago

    Hello. I think the Dev said in another post that the TestFlight purchase is cached, and you may need to delete and reinstall the App Store version to reset it.

  • willya@lemmyf.ukEnglish
    2·
    1 year ago

    Well yeah. The TestFlight version didn’t give you a free sub. It was for testing purposes.

    • a887dcd7a@lemmy.worldOPEnglish
      3·
      1 year ago

      I did not expect anything to be free.

      I expected the correct installed App to reset the testflight’s testing pro status, so I can purchase. Pro was carried over to the production version, where I did not pay, yet.

      This should not happen as anybody with testflight could use this bug to go pro without payment.

      • willya@lemmyf.ukEnglish
        2·
        1 year ago

        Ah, I read it the as you were trying to get it for free. I just checked out my version and the same is true for mine as well. Hmm

        • a887dcd7a@lemmy.worldOPEnglish
          3·
          1 year ago

          Yes. My my name is Karen and I tested this service for free. After a quick chat with the manager I expect to get this service for free indefinitely.

          😂

          Na. Honestly I just wanted dev duo to know that purchasing can be bypassed. But if TestFlight is discontinued, this poses no risk.

    • a887dcd7a@lemmy.worldOPEnglish
      2·
      1 year ago

      Yes and thanks.

      I think I understand the root cause, as the user data is persistent and not invalidated. Also I found a fitting workaround for myself.

      I did not see anything being said about this behavior, but I also did not search in particular.

      If it‘s already been dealt with: the better ☺️