DELETE

[ghost]

DELETE

[Bombastisch]

The Amiibo API switched to HTTPS a few days ago.
Since TagMo is still trying to get the file via HTTP it is failing.

Thos can only be fixed by @HiddenRambler or @North101 with a new update for TagMo.

Until then you will have to do it manually.
Download the .json file from https://www.amiiboapi.com and use the import option in TagMo to load the file.

[D-Pyro]

I was trying to recompile with the changes but because It's so out of date I get a bunch of compile errors. So here's a quick hack to get the existing apk to work.

[Rynelan]

@D-Pyro thanks for the changed apk! I needed that one 😁

[MrHemlock]

I was trying to recompile with the changes but because It's so out of date I get a bunch of compile errors. So here's a quick hack to get the existing apk to work.

@D-Pyro Do you think you could submit the changes you made as a PR? Would be worth it to have that kind of fix on the master build and not just hidden away in an issue.

[D-Pyro]

It's a dirty hack of the original apk. All I did was find the url and added an s. I didn't compile the code.

[Bombastisch]

That's not a dirty hack. Basically that's what is needed to be done. But I can't release a apk with the right key signature because only @HiddenRambler has the key.

[mbirth]

Does the quick hack also include the AmiiboAPI changes? And @Bombastisch, what about releasing the APK with your sig? It's not a big hassle to uninstall the app first before installing your version. Seems like @HiddenRambler is MIA anyways.

[wzhy90]

Another dirty hack, need root and dont need to re-install app or uninstall it.
If U R running android 8 or higher, the patch will be /data/app/com.hiddenramblings.tagmo-[random-base64-string]/oat/arm/base.vdex
android 7 or earlier: /data/dalvik-cache/arm/data@app@/com.hiddenramblings.tagmo-[x]@base.apk@classes.dex

run these command in adb shell or terminal app after force stop the app

cd /data/app/com.hiddenramblings.tagmo-[random-base64-string]/oat/arm/
sed -i "s|http://www.amiiboapi.com/api/amiibo/|https://www.amiiboapi.com/api/amiibo|g" base.vdex

or

cd /data/dalvik-cache/arm
sed -i "s|http://www.amiiboapi.com/api/amiibo/|https://www.amiiboapi.com/api/amiibo|g" data@app@/com.hiddenramblings.tagmo-[x]@base.apk@classes.dex

After that you can sync online.
tested on android 8
PS: if return sh: sed: not found, you need to install busybox first

[Bombastisch]

Fixed in newest release.

[Tymoth]

Hey all,
I was also trying to get the recent Amiibo JSON file for TagMo since the old file is missing a lot of Amiibos. Of course it is still possible to scan and save them as binary file to write it on new Tags, but as I'm a perfectionistc IT-Pro (🤓) I would like to see all properties correctly for all Amiibos. So I compared the old JSON file in my TagMo-App with the new one from AmiiboAPI and recognized the totally changed format of the file. The new one has more properties that were before integrated in the "Title"-Hex Code of the Amiibo. I'm not really experienced with JSON files so I would like to ask you guys if there is an easy way to bring the new JSON Infos in a format that the TagMo 2.7. version would recognize. I will paste a screenshot from JSONdiff, on the left (old) side there are also lines that look like the first ones for "amiibo_series" that contain "type", "character" and so on:

[Bombastisch]

I haven't looked deeper into this, but syncing still works on my phone and I think i also see the correct stats in the amiibo-browser.

Can you elaborate on a certain error you spotted?

[Tymoth]

I tried to import that new JSON file in the official TagMo 2.7 and I get an error while parsing. So there is no chance to get this JSON in 2.7 and I will have to uninstall it and install the 2.6.1 from the Google Drive link in the thread? Sorry but I'm not really familiar with Github and the procedures.
After I compared the old and new JSON format I assumed that it's not possible that any version of TagMo (even with the fixed https, since it will also just download the JSON file I failed to import) can handle it.

[Bombastisch]

I just went into TagMo's in-app settings and hit sync with amiibo API.
Then it displays "syncing was successful" and that's it.
Am I missing something obvious?

[Tymoth]

I got a new phone some days ago (finally Xiaomi Redmi-phones have NFC) and tried again and installed the tagmo 2.6.1 APK but it still can't parse the Amiibo Info with a downloaded .json from amiiboapi and the sync in the app still doesn't work because of the missing https fix. My phone is not rooted, so the method from wzhy90 is also not an option.
@Bombastisch you posted in January that something was fixed in newest release, but I assume that this is already in the 2.6.1 APK that I have on my disk? Or where can I find this fixed version?