stackzy icon indicating copy to clipboard operation
stackzy copied to clipboard

Google Authentication Related Feature does not work

Open wiryadev opened this issue 2 years ago • 3 comments

Login When i tried to login, it shows snackbar with message "NeedsBrowser". image Then i check the logcat and it shows this log. image

Register When i tried to register, the link that i got redirected at gives 404 error. image

Additional Info: Tested both with released .msi in version 1.2.3 and the current master branch which built using IntelliJ. I am using Windows 11.

wiryadev avatar May 19 '22 15:05 wiryadev

I'm facing it aswell. Just make the /Signup in the URL lowercase (/signup) and it will open the google account creation page.

smascaro avatar Sep 14 '22 12:09 smascaro

Same issue on MacOS Ventura (M2 Pro):

org.apache.http.client.ClientProtocolException: NeedsBrowser
	at com.akdeniz.googleplaycrawler.Identity.doPost(Identity.java:181)
	at com.akdeniz.googleplaycrawler.Identity.signIn(Identity.java:142)
	at com.akdeniz.googleplaycrawler.GooglePlayAPI.login(GooglePlayAPI.java:319)
	at com.github.theapache64.gpa.api.Play$login$2.invokeSuspend(Play.kt:39)
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
	at kotlinx.coroutines.internal.LimitedDispatcher.run(LimitedDispatcher.kt:42)
	at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:95)
	at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:570)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:677)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:664)

@smascaro's workaround didn't work

paolorotolo avatar Aug 26 '23 23:08 paolorotolo

The problem with the registration link has been resolved will be accessible in the upcoming version. The login problem may be due to the 2FA feature. Do you guys have 2FA enabled?

theapache64 avatar Feb 27 '24 02:02 theapache64