Member Tools usage without Google Play Services

Discussions around the Android version of the Member Tools application
Post Reply
toQDuj
New Member
Posts: 2
Joined: Sun Dec 20, 2020 12:27 pm

Member Tools usage without Google Play Services

#1

Post by toQDuj »

Hi,

I have updated a new Android device to LineageOS 15.1 (Android 8.1) *without* Google Play Services. Member Tools crashes with errors:

Code: Select all

11-19 07:20:50.958  2056  2080 E ActivityThread: Failed to find provider info for com.google.android.gms.chimera
11-19 07:20:50.960  2056  2080 E DynamiteModule: Failed to load IDynamiteLoader from GmsCore: Application package com.google.android.gms not found
11-19 07:20:50.962  2056  2082 E FirebaseMessaging: Google Play services missing or without correct permission.
11-19 07:20:50.967  2056  2080 E DynamiteModule: Failed to load IDynamiteLoader from GmsCore: Application package com.google.android.gms not found
11-19 07:20:51.406  2056  2098 E         : validateDatabase - table [Unit] is BLANK for database [member.db] is blank
11-19 07:20:51.897  2056  2056 E ResourceType: Style contains key with bad entry: 0x01010586
11-19 07:20:52.769  2056  2098 E         : validateDatabase - table [Unit] is BLANK for database [member.db] is blank
11-19 07:20:55.099  2056  2065 E SpellCheckerSession: ignoring processOrEnqueueTask due to unexpected mState=TASK_CLOSE scp.mWhat=TASK_CLOSE
11-19 07:21:16.577  2056  2235 E Metadata: Google Play services missing or without correct permission.
11-19 07:21:16.670  2056  2183 E         : Unable to generate token for device!
11-19 07:21:16.670  2056  2183 E         : java.io.IOException: java.util.concurrent.ExecutionException: java.io.IOException: MISSING_INSTANCEID_SERVICE
11-19 07:21:16.670  2056  2183 E         :      at com.google.firebase.messaging.FirebaseMessaging.blockingGetToken(com.google.firebase:firebase-messaging@@22.0.0:14)
11-19 07:21:16.670  2056  2183 E         :      at com.google.firebase.messaging.FirebaseMessaging.lambda$getToken$2$FirebaseMessaging(com.google.firebase:firebase-messaging@@22.0.0:1)
11-19 07:21:16.670  2056  2183 E         :      at com.google.firebase.messaging.FirebaseMessaging$$Lambda$3.run(Unknown Source:4)
11-19 07:21:16.670  2056  2183 E         :      at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:457)
11-19 07:21:16.670  2056  2183 E         :      at java.util.concurrent.FutureTask.run(FutureTask.java:266)
11-19 07:21:16.670  2056  2183 E         :      at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:301)
11-19 07:21:16.670  2056  2183 E         :      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
11-19 07:21:16.670  2056  2183 E         :      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
11-19 07:21:16.670  2056  2183 E         :      at com.google.android.gms.common.util.concurrent.zza.run(com.google.android.gms:play-services-basement@@17.6.0:2)
11-19 07:21:16.670  2056  2183 E         :      at java.lang.Thread.run(Thread.java:764)
11-19 07:21:16.670  2056  2183 E         : Caused by: java.util.concurrent.ExecutionException: java.io.IOException: MISSING_INSTANCEID_SERVICE
11-19 07:21:16.670  2056  2183 E         :      at com.google.android.gms.tasks.Tasks.zza(com.google.android.gms:play-services-tasks@@17.2.1:5)
11-19 07:21:16.670  2056  2183 E         :      at com.google.android.gms.tasks.Tasks.await(com.google.android.gms:play-services-tasks@@17.2.1:8)
11-19 07:21:16.670  2056  2183 E         :      at com.google.firebase.messaging.FirebaseMessaging.blockingGetToken(com.google.firebase:firebase-messaging@@22.0.0:10)
11-19 07:21:16.670  2056  2183 E         :      ... 9 more
11-19 07:21:16.670  2056  2183 E         : Caused by: java.io.IOException: MISSING_INSTANCEID_SERVICE
11-19 07:21:16.670  2056  2183 E         :      at com.google.android.gms.cloudmessaging.Rpc.send(com.google.android.gms:play-services-cloud-messaging@@16.0.0:92)
11-19 07:21:16.670  2056  2183 E         :      at com.google.firebase.messaging.GmsRpc.startRpc(com.google.firebase:firebase-messaging@@22.0.0:2)
11-19 07:21:16.670  2056  2183 E         :      at com.google.firebase.messaging.GmsRpc.getToken(com.google.firebase:firebase-messaging@@22.0.0:2)
11-19 07:21:16.670  2056  2183 E         :      at com.google.firebase.messaging.FirebaseMessaging.lambda$blockingGetToken$8$FirebaseMessaging(com.google.firebase:firebase-messaging@@22.0.0:1)
11-19 07:21:16.670  2056  2183 E         :      at com.google.firebase.messaging.FirebaseMessaging$$Lambda$9.start(Unknown Source:4)
11-19 07:21:16.670  2056  2183 E         :      at com.google.firebase.messaging.RequestDeduplicator.getOrStartGetTokenRequest(com.google.firebase:firebase-messaging@@22.0.0:6)
11-19 07:21:16.670  2056  2183 E         :      at com.google.firebase.messaging.FirebaseMessaging.lambda$blockingGetToken$9$FirebaseMessaging(com.google.firebase:firebase-messaging@@22.0.0:1)
11-19 07:21:16.670  2056  2183 E         :      at com.google.firebase.messaging.FirebaseMessaging$$Lambda$8.then(Unknown Source:4)
11-19 07:21:16.670  2056  2183 E         :      at com.google.android.gms.tasks.zze.run(com.google.android.gms:play-services-tasks@@17.2.1:1)
11-19 07:21:16.670  2056  2183 E         :      ... 4 more
I believe this is because Member Tools is too tightly coupled with Google Play Services (GPS). I understand GPS is required for many nice-to-have features, but can these features be made optional and allow the app to continue?

In other words, I am willing to give up features like SMS/Phone/etc. as long as I can still access the calendar and member information. I think in the long run it will be wise to not depend on GPS (like Gospel Living).

Thanks!
Post Reply

Return to “Android Member Tools App”