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

Google signup working as expected for IOS but not for Andriod devices #5362

Open
2 of 14 tasks
sauravkalia opened this issue Aug 25, 2024 · 4 comments
Open
2 of 14 tasks
Labels
Android Issues specific to the Android Platform auth Issues related to the Auth Category pending-community-response Pending response from the issue opener or other community members pending-triage This issue is in the backlog of issues to triage to-be-reproduced Issues that have not been reproduced yet, but have reproduction steps provided

Comments

@sauravkalia
Copy link

sauravkalia commented Aug 25, 2024

Description

I am using Social login(Google and Apple) both are working as expected for IOS bit For Andriod it is getting stuck to the Google Signup browser page.
below I am sharing the AndriodManifest.xml file

<manifest xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:tools="http://schemas.android.com/tools">
    <uses-permission android:name="android.permission.CAMERA"/>
    <uses-permission android:name="android.permission.READ_MEDIA_AUDIO"/>
    <uses-permission android:name="android.permission.READ_MEDIA_IMAGES"/>
    <uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE"/>
    <uses-permission android:name="android.permission.POST_NOTIFICATIONS" />
    <uses-permission android:name="android.permission.INTERNET"/>
    <uses-permission android:name="android.permission.ACCESS_NETWORK_STATE"/>
    <uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />
    <queries>
        <intent>
            <action android:name=
                "android.support.customtabs.action.CustomTabsService" />
        </intent>
    </queries>

    <application
        android:label="SoundStorming"
        android:name="${applicationName}"
        android:icon="@mipmap/ic_launcher" 
        android:theme="@style/NormalTheme">
        <meta-data android:name="com.google.android.geo.API_KEY"
            android:value="@string/google_maps_api_key"/>
        <activity
            android:name=".MainActivity"
            android:exported="true"
            android:launchMode="singleTop"
            android:theme="@style/LaunchTheme"
            android:configChanges="orientation|keyboardHidden|keyboard|screenSize|smallestScreenSize|locale|layoutDirection|fontScale|screenLayout|density|uiMode"
            android:hardwareAccelerated="true"
            android:windowSoftInputMode="adjustResize">
            <!-- Specifies an Android theme to apply to this Activity as soon as
                 the Android process has started. This theme is visible to the user
                 while the Flutter UI initializes. After that, this theme continues
                 to determine the Window background behind the Flutter UI. -->
            <meta-data
              android:name="io.flutter.embedding.android.NormalTheme"
              android:resource="@style/NormalTheme"
              />
            <intent-filter>
                <action android:name="android.intent.action.MAIN"/>
                <category android:name="android.intent.category.LAUNCHER"/>
            </intent-filter>
            <intent-filter>
                <action android:name="android.intent.action.VIEW" />
                <category android:name="android.intent.category.DEFAULT" />
                <category android:name="android.intent.category.BROWSABLE" />
                <data android:scheme="myapp" />
            </intent-filter>
        </activity>
        <activity
            android:name="com.yalantis.ucrop.UCropActivity"
            android:screenOrientation="portrait"
            android:theme="@style/Theme.AppCompat.Light.NoActionBar"
        />
        <!-- Don't delete the meta-data below.
             This is used by the Flutter tool to generate GeneratedPluginRegistrant.java -->
        <meta-data
            android:name="flutterEmbedding"
            android:value="2" />
        <meta-data
            android:name="com.google.firebase.messaging.high_importance_channel"
            android:value="@string/high_importance_channel" />
        <service
            android:name="com.google.firebase.messaging.FirebaseMessagingService"
            android:exported="true"
            tools:replace="android:exported">
            <intent-filter>
                <action android:name="com.google.firebase.MESSAGING_EVENT" />
            </intent-filter>
        </service>
    </application>
</manifest>

Categories

  • Analytics
  • API (REST)
  • API (GraphQL)
  • Auth
  • Authenticator
  • DataStore
  • Notifications (Push)
  • Storage

Steps to Reproduce

These are the logs on Andriod Studio while running Emulator(clicking on signup using Google)

I/flutter (23162): Error signing in: The user cancelled the sign-in flow
D/EGL_emulation(23162): app_time_stats: avg=86.69ms min=1.15ms max=611.47ms count=12
D/EGL_emulation(23162): app_time_stats: avg=3387.94ms min=3387.94ms max=3387.94ms count=1
D/EGL_emulation(23162): app_time_stats: avg=1232.58ms min=8.86ms max=20692.49ms count=17
I/flutter (23162): provider ====> AuthProvider.google
D/AmplifyAuthCognitoPlugin(23162): [launchUrl] Using browser package: com.android.chrome
D/EGL_emulation(23162): app_time_stats: avg=19.51ms min=2.91ms max=161.12ms count=41

Screenshots

No response

Platforms

  • iOS
  • Android
  • Web
  • macOS
  • Windows
  • Linux

Flutter Version

3.22.2

Amplify Flutter Version

2.3.0

Deployment Method

Amplify CLI + Custom Pipeline

Schema

No response

@Jordan-Nelson Jordan-Nelson added auth Issues related to the Auth Category pending-triage This issue is in the backlog of issues to triage labels Aug 26, 2024
@Jordan-Nelson
Copy link
Member

Hello @sauravkalia - I am sorry to hear that you are facing this issue. Was this previously working on Android or are you setting it up for the first time?

@Jordan-Nelson Jordan-Nelson added the pending-community-response Pending response from the issue opener or other community members label Aug 26, 2024
@sauravkalia
Copy link
Author

No, for Andriod I am setting it up for the first time. At first, we went with IOS and didn't face this issue.

@Jordan-Nelson Jordan-Nelson added pending-maintainer-response Pending response from a maintainer of this repository and removed pending-community-response Pending response from the issue opener or other community members labels Aug 27, 2024
@Jordan-Nelson
Copy link
Member

@sauravkalia thanks for the info. I think there is likely something configured incorrectly then but at first glance the AndriodManifest.xml file looks correct. We will look into this and get back to you.

@github-actions github-actions bot removed the pending-maintainer-response Pending response from a maintainer of this repository label Aug 27, 2024
@Jordan-Nelson Jordan-Nelson added to-be-reproduced Issues that have not been reproduced yet, but have reproduction steps provided Android Issues specific to the Android Platform labels Aug 29, 2024
@khatruong2009
Copy link
Member

Hi @sauravkalia, I'm unable to reproduce this issue as Google signup works fine for both my Android and iOS devices when testing. If you're still facing this issue, could you provide us more details about your app configuration?

@khatruong2009 khatruong2009 added the pending-community-response Pending response from the issue opener or other community members label Sep 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Android Issues specific to the Android Platform auth Issues related to the Auth Category pending-community-response Pending response from the issue opener or other community members pending-triage This issue is in the backlog of issues to triage to-be-reproduced Issues that have not been reproduced yet, but have reproduction steps provided
Projects
None yet
Development

No branches or pull requests

3 participants