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

Store Flow Changes (Support for restore flow) #1113

Merged
merged 80 commits into from
Sep 17, 2024
Merged

Conversation

jigar-f
Copy link
Contributor

@jigar-f jigar-f commented Jul 1, 2024

No description provided.

@jigar-f jigar-f marked this pull request as ready for review July 1, 2024 06:25
@jigar-f jigar-f self-assigned this Jul 1, 2024
@jigar-f jigar-f added the WIP label Jul 1, 2024
@jigar-f
Copy link
Contributor Author

jigar-f commented Jul 1, 2024

Got the issue on IOS about the app tracking policy working on that

@jigar-f jigar-f changed the title Uploaded IOS 8.0.0 to TestFlight. IOS 8.0.0 App Store Changes Jul 10, 2024
@@ -36,14 +36,34 @@ class AppMethods {
}

static Future<bool> isPlayStoreEnable() async {
if(!Platform.isAndroid){
if (!Platform.isAndroid) {
return false;
}
final isPlayVersion = sessionModel.isStoreVersion.value ?? false;
Copy link
Contributor

@atavism atavism Sep 3, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tried testing these changes on Android by setting FORCE_PLAY_VERSION=true, and It looks like isPlayVersion always returns false. Are we setting storeVersion on the session model to BuildConfig.PLAY_VERSION?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For me, it is working, Could you confirm that your is not a pro?

@atavism
Copy link
Contributor

atavism commented Sep 3, 2024

I did some testing (by manually setting isPlayVersion to true), and one issue that I encountered is on the restore purchase page, after I enter the email associated with my Pro user along with the subsequent confirmation code, I get an "email not verified" error:

09-03 14:42:21.029 29092 29170 E GoLog   : Sep 03 21:42:21.029 - 29m18s DEBUG defaultwebclient: response.go:66 response body: <error-email-not-verified> status code 500
09-03 14:42:21.030 29092 29191 I GoLog   : Sep 03 21:42:21.029 - 29m18s ERROR proclient: pro.go:371 <error-email-not-verified> status code 500 [error=%v error_location=github.com/getlantern/lantern-client/internalsdk/pro.(*proClient).RestorePurchase (pro.go:371) error_text=<error-email-not-verified> status code 500 error_type=errors.Error]
09-03 14:42:21.030 29092 29191 I GoLog   : ERROR proclient: pro.go:371   at github.com/getlantern/lantern-client/internalsdk/pro.(*proClient).RestorePurchase (pro.go:371)
09-03 14:42:21.030 29092 29191 I GoLog   : ERROR proclient: pro.go:371   at github.com/getlantern/lantern-client/internalsdk.restorePurchase (session_model.go:1553)
09-03 14:42:21.030 29092 29191 I GoLog   : ERROR proclient: pro.go:371   at github.com/getlantern/lantern-client/internalsdk.(*SessionModel).doInvokeMethod (session_model.go:346)
09-03 14:42:21.030 29092 29191 I GoLog   : ERROR proclient: pro.go:371   at github.com/getlantern/lantern-client/internalsdk.(*baseModel).InvokeMethod (model.go:103)
09-03 14:42:21.030 29092 29191 I GoLog   : ERROR proclient: pro.go:371   at main.proxyinternalsdk_SessionModel_InvokeMethod (go_internalsdkmain.go:669)
09-03 14:42:21.030 29092 29191 I GoLog   : ERROR proclient: pro.go:371   at _cgoexp_7a18dc8f8e4b_proxyinternalsdk_SessionModel_InvokeMethod (_cgo_gotypes.go:2494)
09-03 14:42:21.030 29092 29191 I GoLog   : ERROR proclient: pro.go:371   at runtime.cgocallbackg1 (cgocall.go:420)
09-03 14:42:21.030 29092 29191 I GoLog   : ERROR proclient: pro.go:371   at runtime.cgocallbackg (cgocall.go:339)
09-03 14:42:21.030 29092 29191 I GoLog   : ERROR proclient: pro.go:371   at runtime.cgocallback (asm_arm64.s:1130)
09-03 14:42:21.030 29092 29191 I GoLog   : ERROR proclient: pro.go:371   at runtime.goexit (asm_arm64.s:1222)
09-03 14:42:21.030 29092 29191 I GoLog   : ERROR proclient: pro.go:371 Caused by: <error-email-not-verified> status code 500

This may be unrelated to this PR, but I wonder if the pro server may not be updating users to have verified email addresses after they enter a valid confirmation code (unless I'm getting that error for some other reason?).

@jigar-f
Copy link
Contributor Author

jigar-f commented Sep 4, 2024

I did some testing (by manually setting isPlayVersion to true), and one issue that I encountered is on the restore purchase page, after I enter the email associated with my Pro user along with the subsequent confirmation code, I get an "email not verified" error:

09-03 14:42:21.029 29092 29170 E GoLog   : Sep 03 21:42:21.029 - 29m18s DEBUG defaultwebclient: response.go:66 response body: <error-email-not-verified> status code 500
09-03 14:42:21.030 29092 29191 I GoLog   : Sep 03 21:42:21.029 - 29m18s ERROR proclient: pro.go:371 <error-email-not-verified> status code 500 [error=%v error_location=github.com/getlantern/lantern-client/internalsdk/pro.(*proClient).RestorePurchase (pro.go:371) error_text=<error-email-not-verified> status code 500 error_type=errors.Error]
09-03 14:42:21.030 29092 29191 I GoLog   : ERROR proclient: pro.go:371   at github.com/getlantern/lantern-client/internalsdk/pro.(*proClient).RestorePurchase (pro.go:371)
09-03 14:42:21.030 29092 29191 I GoLog   : ERROR proclient: pro.go:371   at github.com/getlantern/lantern-client/internalsdk.restorePurchase (session_model.go:1553)
09-03 14:42:21.030 29092 29191 I GoLog   : ERROR proclient: pro.go:371   at github.com/getlantern/lantern-client/internalsdk.(*SessionModel).doInvokeMethod (session_model.go:346)
09-03 14:42:21.030 29092 29191 I GoLog   : ERROR proclient: pro.go:371   at github.com/getlantern/lantern-client/internalsdk.(*baseModel).InvokeMethod (model.go:103)
09-03 14:42:21.030 29092 29191 I GoLog   : ERROR proclient: pro.go:371   at main.proxyinternalsdk_SessionModel_InvokeMethod (go_internalsdkmain.go:669)
09-03 14:42:21.030 29092 29191 I GoLog   : ERROR proclient: pro.go:371   at _cgoexp_7a18dc8f8e4b_proxyinternalsdk_SessionModel_InvokeMethod (_cgo_gotypes.go:2494)
09-03 14:42:21.030 29092 29191 I GoLog   : ERROR proclient: pro.go:371   at runtime.cgocallbackg1 (cgocall.go:420)
09-03 14:42:21.030 29092 29191 I GoLog   : ERROR proclient: pro.go:371   at runtime.cgocallbackg (cgocall.go:339)
09-03 14:42:21.030 29092 29191 I GoLog   : ERROR proclient: pro.go:371   at runtime.cgocallback (asm_arm64.s:1130)
09-03 14:42:21.030 29092 29191 I GoLog   : ERROR proclient: pro.go:371   at runtime.goexit (asm_arm64.s:1222)
09-03 14:42:21.030 29092 29191 I GoLog   : ERROR proclient: pro.go:371 Caused by: <error-email-not-verified> status code 500

This may be unrelated to this PR, but I wonder if the pro server may not be updating users to have verified email addresses after they enter a valid confirmation code (unless I'm getting that error for some other reason?).

This is correct, You get this error only when you enter an expired code while verification. Can you try again and see if that's an issue, it should work.

@jigar-f
Copy link
Contributor Author

jigar-f commented Sep 13, 2024

@atavism Could you review this?

@jigar-f jigar-f removed the on hold label Sep 13, 2024
@jigar-f
Copy link
Contributor Author

jigar-f commented Sep 16, 2024

@atavism Could you please give this PR spin? I like to merge this if all okay

@jigar-f jigar-f merged commit 9d91f1c into main Sep 17, 2024
2 checks passed
@jigar-f jigar-f deleted the jigar/ios-upload-8.0 branch September 17, 2024 06:10
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

Successfully merging this pull request may close these issues.

2 participants