after OAuth the browser popup doesnt close but the user is logged in, what could be the issue?
#OAuth Browser Popup doesn't close
empty wharf
login session is created using:
await account.createOAuth2Session(provider: OAuthProvider.google);
AndroidManifest is configured properly:
<activity android:exported="true" android:name="com.linusu.flutter_web_auth_2.CallbackActivity">
<intent-filter android:label="flutter_web_auth_2">
<action android:name="android.intent.action.VIEW" />
<category android:name="android.intent.category.DEFAULT" />
<category android:name="android.intent.category.BROWSABLE" />
<data android:scheme="appwrite-callback-${PROJECT_ID}" />
</intent-filter>
</activity>
Project ID is in this form as it gets injected during a CI/CD Workflow, and it is added to manifestPlaceholders by the Gradle Build:
val projectId: String = System.getenv("APPWRITE_PROJECT_ID")
manifestPlaceholders += mapOf( "PROJECT_ID" to projectId )
Hey @past oak I'm sorry for the tag but I really need some help with this, I'm waiting on this to push an update to my app so users can login with OAuth, which is currently broken.
empty wharf
Seems to be a transitive issue from flutter_web_auth_2, fixed by using
dependency_overrides:
flutter_web_auth_2: ^5.0.0-alpha.3
@slow scroll @novel kraken You guys might wanna take a look at this
slow scroll
Seems to be a transitive issue from flutter_web_auth_2, fixed by using
```yaml
...
I see.
I will raise a PR to fix this
Well. Do if you prefer or want! 😅
empty wharf
flutter_web_auth_2 is changing the method of authenticating on Android completely in v5
There are no breaking changes though
empty wharf
Well. Do if you prefer or want! 😅
Sure, could you please point me to the repo? The flutter sdk repo seems to be read only
empty wharf
There are no breaking changes though
Since the version I used is still in alpha and v5 as a whole is still in Alpha, maybe it would be better to wait for a GA release? Upto you guys how you wanna handle this, but maybe another potential solution can be adding to the documentation temporarily to use a dependency override if someone faces an issue.
The reason I propose this alternate approach is, if someone has an issue with the alpha then they will be confused.
Although that is unlikely
empty wharf
https://github.com/appwrite/sdk-generator/tree/master/templates%2Fflutter
Thank You
slow scroll
Since the version I used is still in alpha and v5 as a whole is still in Alpha, ...
It's critical. Better using alpha
empty wharf
https://github.com/appwrite/sdk-generator/pull/1254
Here you go. Thanks for the oppurtunity!