-
Notifications
You must be signed in to change notification settings - Fork 0
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
Getting error after authorization- Failed to handle method call #5
Comments
…mbedding does not support the old FlutterView. at io.flutter.embedding.engine.plugins.shim.ShimRegistrar.view(ShimRegistrar.java:82)
Could you please try the git version by replacing the dependency to pub.dev's oauth2_custom_uri_scheme with the following one: oauth2_custom_uri_scheme:
git:
https://github.com/espresso3389/oauth2_custom_uri_scheme If it works for you, I'll publish a new package as soon as possible. |
Sorry, the previous commit does not fix the issue and 7d4d869 (0.3.8) finally fixes the issue. |
Thanks @espresso3389 Tried all versions 0.3.6, 0.3.8 and 0.3.9 Application getting crashed, if exclude/comment oauth2_custom_uri_scheme application is working fine. Attached sample project, Could you please check the issue? |
Woops, We're hitting the issue just now...
|
There's a release blocker and I just released a release, 0.3.10 which is based on 0.3.6 (the code is not changed) so it's anyway not fixing any things but it just work on certain environments. So if you want to check the latest version, please use the latest github commit. I think the following commit will work: oauth2_custom_uri_scheme:
git:
url: https://github.com/espresso3389/oauth2_custom_uri_scheme
ref: a94d9e76001fb09c4761eda47fd47ecdca9f08e4 |
0.4.3 introduces flutter_inappwebview 4.0.0 and the issue is fixed. |
Trying to authorization using Microsoft office 365 account,
Error:
E/MethodChannel#oauth2_custom_uri_scheme( 481): Failed to handle method call
E/MethodChannel#oauth2_custom_uri_scheme( 481): java.lang.UnsupportedOperationException: The new embedding does not support the old FlutterView.
E/MethodChannel#oauth2_custom_uri_scheme( 481): at io.flutter.embedding.engine.plugins.shim.ShimRegistrar.view(ShimRegistrar.java:82)
E/MethodChannel#oauth2_custom_uri_scheme( 481): at jp.espresso3389.oauth2_custom_uri_scheme.Oauth2CustomUriSchemePlugin.onMethodCall(Oauth2CustomUriSchemePlugin.kt:53)
E/MethodChannel#oauth2_custom_uri_scheme( 481): at io.flutter.plugin.common.MethodChannel$IncomingMethodCallHandler.onMessage(MethodChannel.java:231)
E/MethodChannel#oauth2_custom_uri_scheme( 481): at io.flutter.embedding.engine.dart.DartMessenger.handleMessageFromDart(DartMessenger.java:93)
E/MethodChannel#oauth2_custom_uri_scheme( 481): at io.flutter.embedding.engine.FlutterJNI.handlePlatformMessage(FlutterJNI.java:642)
E/MethodChannel#oauth2_custom_uri_scheme( 481): at android.os.MessageQueue.nativePollOnce(Native Method)
E/MethodChannel#oauth2_custom_uri_scheme( 481): at android.os.MessageQueue.next(MessageQueue.java:325)
E/MethodChannel#oauth2_custom_uri_scheme( 481): at android.os.Looper.loop(Looper.java:142)
E/MethodChannel#oauth2_custom_uri_scheme( 481): at android.app.ActivityThread.main(ActivityThread.java:6626)
E/MethodChannel#oauth2_custom_uri_scheme( 481): at java.lang.reflect.Method.invoke(Native Method)
E/MethodChannel#oauth2_custom_uri_scheme( 481): at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438)
E/MethodChannel#oauth2_custom_uri_scheme( 481): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:811)
I/flutter ( 481): PlatformException(error, The new embedding does not support the old FlutterView., null)
Configuration:
final oauth2Config = OAuth2Config(
uniqueId: 'example.com#1',
authorizationEndpoint: Uri.parse("https://login.microsoftonline.com/common/oauth2/v2.0/authorize"),
tokenEndpoint: Uri.parse("https://login.microsoftonline.com/common/oauth2/v2.0/token"),
);
Android Manifest.xml:
Microsoft Office 365 Redirect URI configuration:
Not able to get token after authorization.
Please let me know, how to resolve the issue and get token.
The text was updated successfully, but these errors were encountered: