You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I stumbled upon an issue with the Sumup.loginWithToken method.
This is my function:
Future<void> initializeAndLoginSumUp() async {
final isStillLoggedIn =awaitSumup.isLoggedIn;
if (isStillLoggedIn !=null) {
if (isStillLoggedIn) {
_isLoggedIn =true;
notifyListeners();
return;
} else {
//final response = await Sumup.loginWithToken(apiToken);final response =awaitSumup.login();
final message = response.message;
if (message !=null) {
if (message['loginResult'] ==true) {
_isLoggedIn =true;
}
}
notifyListeners();
}
}
}
It is called everytime before I make an transaction within my application. Once a session expires and I relog with the line that is currently commented out, the login succeeds but when trying to process a checkout, it results in "Invalid access token" error and fails.
It works fine with the regular login method though!
Hope I was able to explain my issue somewhat understandable.
Best regards
The text was updated successfully, but these errors were encountered:
Hey, thanks for your answer. Unfortunately I don't use the API calls in my App. I was trying to make it work with the things the SDK natively provides. If I have to do it using URL requests & parameters, why would I use the SDK in the first place?
I meant that the token might have been generated in a wrong way, as discussed in that thread. Also, check that your OAuth app has all the required scopes, I think you need the 'payments' scope.
Hello everyone,
I stumbled upon an issue with the Sumup.loginWithToken method.
This is my function:
It is called everytime before I make an transaction within my application. Once a session expires and I relog with the line that is currently commented out, the login succeeds but when trying to process a checkout, it results in "Invalid access token" error and fails.
It works fine with the regular login method though!
Hope I was able to explain my issue somewhat understandable.
Best regards
The text was updated successfully, but these errors were encountered: