Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[issue] Ensuring Successful In-App Credit Purchases on iOS Devices #3198

Open
sync-by-unito bot opened this issue Feb 5, 2024 · 16 comments
Open

[issue] Ensuring Successful In-App Credit Purchases on iOS Devices #3198

sync-by-unito bot opened this issue Feb 5, 2024 · 16 comments

Comments

@sync-by-unito
Copy link

sync-by-unito bot commented Feb 5, 2024

User story

As an iOS user of Capture Cam,

I want to successfully purchase credits through in-app purchases,

So that I can enhance my usage capabilities within the app without facing transaction issues.

Reproduce step

  1. Open Capture Cam
  2. Press "Buy Credits"
  3. Choose one of options
  4. Payment was successful, but credits did not increase also doesn't display any error message.

Expectation

User should pay by credit card & get credits through in-app purchase.

Additional information:

Only happened on iOS device.

┆Issue is synchronized with this Asana task by Unito
┆Created By: Kenny Hung

Copy link
Author

sync-by-unito bot commented Feb 5, 2024

➤ Sherry Chung commented:

I checked both iOS & android in the morning. It’ll quickly show an error, then it can show the purchase items as usual (but I didn’t really do the purchase).

Copy link
Author

sync-by-unito bot commented Feb 5, 2024

➤ Sam commented:

It’s showing error when app is launched or in buy bum page?

Copy link
Author

sync-by-unito bot commented Feb 5, 2024

➤ Sherry Chung commented:

  1. User click "... meny" -> "Wallet"
  2. Click "Buy Credits"
  3. Quickly show an error "in-app purchase is not available e now...."
  4. Show normal options for different packages with in-App purchase.

Copy link
Author

sync-by-unito bot commented Feb 5, 2024

➤ James Chien commented:

The task description is an issue happened when Cam communicates with backend.

The above in-app purchase is not available now.... is an issue happened on Cam, might related to Bubble price API or iOS product config, and not related to backend.

This two issue are differently scoped.

Copy link
Author

sync-by-unito bot commented Feb 6, 2024

➤ Sam commented:

Sherry Chung what you are referring ( https://app.asana.com/0/0/1206518277335299/1206518360572032/f ) to is not really an error it's just a message to say that in app purchase products are loading.

But I agree it's quite confusing therefore I have suggest enhancement proposal ( https://app.asana.com/0/1201016280880500/1206531905253688/f ) and I will make sure with QA to arrange [Quality/Performance] For in app purchase products show loading indicator first ( https://app.asana.com/0/1201016280880500/1206531905253688/f ) to future sprints.

Please feel free to close this task if there are no other issue related to backend etc.

Copy link
Author

sync-by-unito bot commented Feb 6, 2024

➤ Sherry Chung commented:

After discussion with James Chien. The issue that user purchased in-app purchase in iOS but didn't receive credits.

It might need to check the Capture Cam site.

Since this is not in the goal of Sprint 24.01.29 kickoff ( https://app.asana.com/0/0/1206458446271108 ) and still need further testing tor clarify the issue.

Suggest to move this to next sprint.

(And thanks for Sam 's help to open another task with [Quality/Performance] For in app purchase products show loading indicator first ( https://app.asana.com/0/1201016280880500/1206531905253688 ) )

Copy link
Author

sync-by-unito bot commented Feb 6, 2024

➤ James Chien commented:

Kenny Hung I live-edited log collection to get receipt_id from log. Could you help try an iOS purchase so I can collect the receipt_id from backend?

Copy link
Author

sync-by-unito bot commented Feb 6, 2024

➤ Kenny Hung commented:

James Chien You mean try live version Capture Cam?

Copy link
Author

sync-by-unito bot commented Feb 6, 2024

➤ James Chien commented:

Kenny Hung Yes, live verison. There's some error when parsing the request body in previous setup so I didn't get the log. Can we arrange a huddle and do it together so I can get the request body Capture Cam sent?

Copy link
Author

sync-by-unito bot commented Feb 6, 2024

➤ Tammy Yang commented:

The in-app purchase is handled by ionic side, should you talk to Sam?

Copy link
Author

sync-by-unito bot commented Feb 6, 2024

➤ Sam commented:

I believe what James want is to get request body form real receipt (real receipt are generated when actual money is spent so maybe that’s why he need Kenny)

But let me know if I can assist in some way

Copy link
Author

sync-by-unito bot commented Feb 6, 2024

➤ James Chien commented:

SamTammy Yang Yes. If Sam could help getting the receipt_id in request body it would be great. Otherwise I can try to fetch it from backend when the live version performs purchase.

Sam by the way, I found many iOS purchase API calls are performed twice in 2-3 seconds , the first one will succeed, the second one will fail due to duplicate error. If you know anything about this behavior on Capture Cam site please let me know.

Copy link
Author

sync-by-unito bot commented Feb 6, 2024

➤ James Chien commented:

Kenny Hung 台灣時間 14:52 的是 invalid receipt

16:55 的購買有成功,只是 Cam 送了第二次 request ,第二次因為 duplicate receipt id 回傳失敗,應該有入帳 15 credits

Copy link
Author

sync-by-unito bot commented Feb 6, 2024

➤ Tammy Yang commented:

Lower priority, move to the sprint after LNY.

Copy link
Author

sync-by-unito bot commented Feb 7, 2024

➤ Sam commented:

James Chien regarding Comment by @james Chien on [issue] Ensuring Successful In-App Credit Purchases on iOS Devices ( https://app.asana.com/0/0/1206518277335299/1206525052489855/f ) I mentioned in codebase before ( https://github.com/numbersprotocol/capture-lite/blob/v240206-capture-cam-ionic-internal/src/app/shared/in-app-store/in-app-store.service.ts#L145 ) it might be more of a plugin issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

0 participants