TomTom AmiGO app incompatibility

[ameshkov]

@VincenzoVitale-TomTom commented on Fri Jan 15 2021

Hello,
multiple users of the TomTom AmiGO app are reporting problems when AdGuard is used.
In AmiGO we use certificate pinning to restrict to a minimum the accepted certificates, that is why the HTTP filtering in AdGuard causes requests to fail.

AmiGO is a free navigation application with no advertisement and TomTom will never sell customer data to others. That is also what differentiate the AmiGO app (and the entire TomTom) from other free navigation applications.

As also discussed by email, could you please add the following urls to the exclusion list:

scmts.tomtom.com
api.tomtom.com
test.api-system.tomtom.com/ (nk2 we use in beta)
appanalytics.tomtom.com
www.leanplum.com

Important note, we tried to add the URLs in AdGuard to check if that would solve the problems, but the app still didn't work.
The only action that seemed to work was when we requested AdGuard to not block the entire app.
Is it possible to add an entire verified application to a default exclusion list?

Thanks,
V.

---

@ameshkov commented on Fri Jan 15 2021

Got it, thank you for reporting it!

Is it possible to add an entire verified application to a default exclusion list?

Yes, I guess it'd be easier to disable HTTPS filtering for the app by default.
However, users may still decide to enable it on their own (even though AdGuard will warn them that this is not recommended).

One important note here - by default AdGuard does not attempt to filter HTTPS in apps that target SDK level 23 or higher unless the user has root access and manually moved AdGuard CA to the system certs store. This is just a tiny share of all users, everything should be okay for others.

[ameshkov]

@artemiv4nov until the underlying issue is fixed in CoreLibs, I suggest disabling "ad blocking" for this app by default.

Later, when this issue is properly addressed in CoreLibs (AdguardTeam/CoreLibs#1399), we can remove that temporary exception.

[VincenzoVitale-TomTom]

Hello, I see the resolved status. Will this be released in the next adguard version?

[ameshkov]

@VincenzoVitale-TomTom yep, we're going to push the update next week

[VincenzoVitale-TomTom]

Amazing, thanks a lot

[VincenzoVitale-TomTom]

Upgraded to the latest version (3.6.1) and I'm happy to confirm that AmiGO is now working without the need to change anything in AdGuard.
We'll contact our users who had reported problems to make sure they enable AdGuard again in case they had switched it off to use AmiGO.

Unfortunately folks who downloaded AmiGO via the Huawei app gallery still have the problem.
My bad, since I didn't think/remember that in the huawei app gallery we are uploading AmiGO with a different package id (and signed with a different certificate) and I never told you.
@ameshkov Would it be possible in the next adguard release to apply the same exception for
com.tomtom.amigo.huawei
?

Thanks a lot,
V.

[ameshkov]

@VincenzoVitale-TomTom yep, I've opened a new one: #3767

[woody4165]

Still having issue when calculating itinerary.
Adguard 3.6.1 and Amigo 7.456 on Xiaomi phone.
Now maps show correctly despite previous versions of Tomtom app, but still gives error when searching for a destination.
As soon as I deactivate Adguard, it works perfectly.

[ameshkov]

@woody4165 thanks for the feedback! We'll check it, mentioned your report in the new issue.