microg / microg/GmsCore

unable to login Targobank

Open
#912 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
14.6k
Forks
3.2k
Avg merge
12d 11h
Merged PRs (30d)
4

Description

App loads continuously after putting in login.
Exception in log related to gms that I found:

Attempt to cast generated internal exception:
java.lang.ClassCastException: java.lang.Double cannot be cast to java.lang.Long
at android.os.BaseBundle.getLong(BaseBundle.java:1070)
at android.os.BaseBundle.getLong(BaseBundle.java:1052)
at com.google.android.gms.measurement.internal.zzda.zza(Unknown Source:172)
at com.google.android.gms.measurement.internal.zzda.zza(Unknown Source:679)
at com.google.android.gms.measurement.internal.zzdc.run(Unknown Source:2)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:458)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at com.google.android.gms.measurement.internal.zzbv.run(Unknown Source:20)

Gms_class_cast_exception_targo.txt

Edit: To clearfy clarify. I am not using any google account credentials. This is all happing when using Targobank account credentials.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the attached Gms_class_cast_exception_targo.txt log and the Google Mobile Services login path used when Targobank credentials are submitted. Reproduce the continuously loading login and determine whether the reported ClassCastException is part of the failure; done means the Targobank login completes without the loading loop.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java
Domain
authentication, mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.