Issue Report: Login Button Not Functioning

[ankitkumar1302]

Issue Report: Login Button Not Functioning

Issue Description: When attempting to log in by clicking the login button, the expected behaviour of a bottom sheet listing accounts does not occur. Despite waiting for an extended period, no response or UI element appears.

Steps to Reproduce: 1) Navigate to the login page of the project. 2) Click on the login button. 3) Observe the absence of any bottom sheet or account listing appearing.

Expected Behavior: After clicking the login button, a bottom sheet should appear listing the available accounts for login.

Actual Behavior: Nothing happens after clicking the login button. No bottom sheet or account listing is shown.

Additional Information: A video demonstrating this issue has been attached to this report for further clarity.

Attachments:

https://github.com/stevdza-san/DiaryApp/assets/95230112/c6a30f1d-7f15-41a6-8e59-7348a40b8344

Environment:

Project Version: Latest Operating System: Android 10

[stevdza-san]

Check the logs for "OneTapCompose" tag, to see some more information when trying to sign in.

[ankitkumar1302]

When I paste this tag i get these logs:-

2024-07-03 01:40:36.964 11400-11400 FloatService com.miui.notes D onPrimaryClipChanged OneTapCompose 2024-07-03 01:40:36.998 11400-11400 FloatService com.miui.notes D onPrimaryClipChanged OneTapCompose 2024-07-03 01:42:13.929 11400-11400 FloatService com.miui.notes D onPrimaryClipChanged 2024-07-03 01:40:36.964 11400-11400 FloatService com.miui.notes D onPrimaryClipChanged OneTapCompose 2024-07-03 01:40:36.998 11400-11400 FloatService com.miui.notes D onPrimaryClipChanged OneTapCompose 2024-07-03 01:42:13.933 11400-11400 FloatService com.miui.notes D onPrimaryClipChanged 2024-07-03 01:40:36.964 11400-11400 FloatService com.miui.notes D onPrimaryClipChanged OneTapCompose 2024-07-03 01:40:36.998 11400-11400 FloatService com.miui.notes D onPrimaryClipChanged OneTapCompose

What to do should I bypass this ? or something else.

[JakeBasa]

have you found a solution for this?

[ankitkumar1302]

No, I did not find a solution for that, I think there are some other dependencies have to use to solve this or can modify the code to bypass this login function or straight goes to the app

[stevdza-san]

Usually that can happen because of the misconfigured google authentication provider, then because your device doesn't support Credential Manager API, or maybe your google account doesn't have enabled sign in prompts in the settings (https://myaccount.google.com/connections/settings?continue=https%3A%2F%2Fmyaccount.google.com%2Fdata-and-privacy). Either way you should be able to see some kind of an information in the logs when you click the button.

[stevdza-san]

@JakeBasa Update the OneTapCompose library to 1.0.13, and check the logs after you press the button. Be sure to include your project's SHA-1 fingerprint and the package name in your Google Cloud Project.

[stevdza-san]

That probably means you need to double check your Google Cloud project and see if you've configured it correctly. Remember you do need to use WEB client id in your app. Also double check if you're using the correct project package name, as well as SHA-1 fingerprint (in Android OAuth client)

[stevdza-san]

@JakeBasa No, just go to the google cloud platform and create the project for free. I've made a video tutorial about it as well: https://youtu.be/QpaTcx2nnHM?si=PA9d5wJgrRA4gV3p

[stevdza-san]

@JakeBasa Ah, this error indicates that you already have a project on the Google Cloud Platform, that uses the same package name/SHA-1 fingerprint. Be sure that each project on the platform, includes unique package name.

[stevdza-san]

That error indicates that you have probably some permission issues on MongoDB Atlas. Check the logs first.