microg / microg/GmsCore

Phenotype.API is not available on this device

Open
#597 2 comments 2 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

[ 08-28 20:39:53.179  3602: 3719 E/PhenotypeFlagCommitter ]
Retrieving snapshot for com.google.android.gm failed
java.util.concurrent.ExecutionException: hpl: 17: API: Phenotype.API is not available on this device.
	at jbz.a(Unknown Source)
	at jbz.a(Unknown Source)
	at iyh.a(Unknown Source)
	at cwp.run(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
	at java.lang.Thread.run(Thread.java:761)
Caused by: hpl: 17: API: Phenotype.API is not available on this device.
	at hvj.a(Unknown Source)
	at htb.a(Unknown Source)
	at hsz.a(Unknown Source)
	at hrm.a(Unknown Source)
	at hrm.a(Unknown Source)
	at hwd.a(Unknown Source)
	at hwj.a(Unknown Source)
	at hwb.a(Unknown Source)
	at hwe.handleMessage(Unknown Source)
	at android.os.Handler.dispatchMessage(Handler.java:102)
	at android.os.Looper.loop(Looper.java:154)
	at android.os.HandlerThread.run(HandlerThread.java:61)

[ 08-28 20:39:53.209  3272: 3292 D/GmsClearcutLogSvcImpl ]
log: LogEventParcelable[1, PlayLoggerContext[1, package=com.google.android.gm, packageVersionCode=60575153, logSource=-1, uploadAccount=null, loggingId=-1, logAndroidId=true, logSourceName=GMAIL_ANDROID_PRIMES, isAnonymous=false, qosTier=0], LogEventBytes: [letters_and_numbers], AddPhenotypeExperimentTokens: true]

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

No source files, tests, or entry points are named. Start by reproducing the supplied Gmail log on the affected Android device and tracing the Phenotype.API implementation in GmsCore. Done means the reported API-unavailable error is resolved for that scenario.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java
Domain
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.