Apple Purchase workflow testing

[textual]

I've got a few questions about how this is supposed to work, and would be willing to have an offline discussion if needed. I thought I understood the overall workflow but then when it comes to testing, I'm getting some results that I'm a little confused about.

1. accessing the app as different users. my intention is to have a login, and then when a user purchases a subscription, i update my database and thats that. but i guess the subscription is really to the phone account, so if im testing as another user (log out and log in as another app account), it thinks I'm already subscribed. and then i get a flood of purchase receipts from the event listener

2. accepting the purchase via app or server. i think the intended workflow is for my app to request purchase, my app receive the purchase receipt, my app send that receipt to my server for processing, my server sends to my app a success response, and hten my app sends the finish back to apple. this is when theres no active subscriptions from phone user like above. otherwise i get an error

3. capturing errors deftly. i thought i had proper coverage but i still get error about undefined things. to be clear, i make the requestSubscribe call and then either the event listener or error handler would be triggered, for things like

• user canceled
• already subscribed
• apple server not responding
• or successful purchase that needs to be sent a finish call

If receiving a flood of purchase messages for a single users subscription testing seems normal, maybe i just need to work out these kinks. but any tips around avoiding these pitfalls would be greatly appreciated