Path: news.eternal-september.org!eternal-september.org!feeder3.eternal-september.org!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!nnrp.usenet.blueworldhosting.com!.POSTED!not-for-mail
From: Marion <marion@facts.com>
Newsgroups: comp.mobile.android
Subject: Re: Who updated the last known good version of this app on my phone?
Date: Tue, 1 Jul 2025 19:36:42 -0000 (UTC)
Organization: BWH Usenet Archive (https://usenet.blueworldhosting.com)
Message-ID: <1041dc9$12mu$1@nnrp.usenet.blueworldhosting.com>
References: <10419gk$1f0u$1@nnrp.usenet.blueworldhosting.com> <1041csd$v2p$1@nnrp.usenet.blueworldhosting.com>
Injection-Date: Tue, 1 Jul 2025 19:36:42 -0000 (UTC)
Injection-Info: nnrp.usenet.blueworldhosting.com;
	logging-data="35550"; mail-complaints-to="usenet@blueworldhosting.com"
User-Agent: ForteAgent/8.00.32.1272
Cancel-Lock: sha1:QydQHPQnHHns/zXjd5uztpeLIgg= sha256:bipJ8gOWBSxWHsR+NKXHfv1hhMuKxrbjoj+sfThqAVA=
	sha1:9vYfjzAN4zewL68f5t17LoA64qw= sha256:sZHSr11sZxiRV0DKvyhbgnXAifqRO38xRQ6Ix6nyTm8=

On Tue, 1 Jul 2025 19:28:13 -0000 (UTC), Marion wrote :


> Q1: How can I check how this update happened?
> Q2: And how can I put a stop to this nonsense?

Apparently, had I been running adb logcat when the update occurred, it
might have caught the specific process that initiated the update. 

Then all I'd need to do is filter for tags like "Finsky" (Google Play),
"PackageManager," or the app's package name (xyz.klinker.messenger).
 adb logcat | findstr "Finsky"
 adb logcat | findstr "PackageManager"
 adb logcat | findstr "xyz.klinker.messenger"

The problem is I don't leave logcat running for unexpected happenings.

My guess is the update originated from Google Play Services, perhaps
leveraging hidden in-app update capabilities built into the Pulse SMS app.

I probably should have NOT wiped out the Maple Media version until I
checked the Firebase App Indexing data. My bad.

Next time I'll do the queries BEFORE I replace the app with the last known
good version.