Both Amiigo and Emutool source Amiibo data from the Amiibo API. If there's a mislabeled Amiibo it's an issue with that. You could try opening an issue on their GitHub.
Damn that's a segfault. Kind of a pain in the ass to debug remotely. Would you be able to send me a crash log? Should be in sdmc:/atmosphere/fatal_reports
By deleting the configuration folder, the software is launched. thanks a lot for your help
Aww. I hate debugging network stuff. Oh well at least I know the issue is in the networking code now, just need to use that stack addresses to figure out where exactly. Fwiw since it's in the networking code starting Amiigo in airplane mode after deleting the config should work around it since Amiigo will use local copies of files it usually retrieves from the internet if it goes a certain amount of time (20 seconds iirc) without an internet connection. Just wait when it says "waiting for connection" and it should skip all the networking stuff. Depending on what the bug is you might only need to go in to airplane once when you first launch it.
No problem. That stuff has caused a bunch of problems in the past so I had a hunch but I thought I had figured it all out now. Oh well. Once I work out what it is I'll release 1.3.1 to patch it if anyone else has that issue.
I changed the network configuration because of the bug then deleted the folder you mentioned above and the Amiigo now launches. Thanks again, I've been looking all afternoon.
There isn't enough information in here to properly debug the issue. Running all those stack addresses through addr2line doesn't give any functions that I wrote myself, I guess because it is actually a system module that's crashing and not Amiigo itself. I do have a rough idea of where the bug is though so I'll keep looking for it. Let me know if you get the same issue again in the future and we'll see what info we can squeeze out of your console if I haven't figured out what it is before then.
Error 0x4A2 (2162-0002) definitely isn't related to Amiigo so you shouldn't break your head over it.
I think it is an Amiigo issue. 0x4A2 is a generic system module error. I initially misread it as 0x4A8 which would be a segfault, explains why the fatal screen is missing register data which is usually included in segfault reports. We know it's definitely not theme related because the title ID in the image is 0100000000000012 which SwitchBrew says is bsdsockets but themes are handled by qlaunch (title ID 0100000000001000). Also the crash report says so. I'm probably passing incorrect (or corrupted) data in to the networking system module and it doesn't know what to do with it so it throws a generic error since it can't possibly have a dedicated error code for every possible thing that could go wrong in such a huge codebase (not without making error codes use more digits at least).
After lots of debugging I have discovered that the issue is actually in how nlohmann's JSON library handles corrupt data. For some reason it relies on BSD sockets even if the system is offline, and if the data is malformed it causes crashes. Malformed data might come from the connection being interrupted while it's caching the Amiibo API. I do have a fixed version of Amiigo but I'm very tired so I'm probably going to start over from scratch tomorrow to make sure I'm not introducing any other bugs by fixing this one. It should be easy now that I know what the issue is.
FYI, the bug occurred when I updated Emiibo, switched to Amiigo (I used Amiiswap) and used ccproxy to block incoming connections. I haven't used a theme for several years and my SD card is perfectly formatted.
I'll look in to this when I can, but right now my Switch is bricked because the dat0 cable came loose and I don't have the tools to reattach it. Might be a few weeks, sorry.
No problem, after clicking on the Super Smash Bros category I get a black screen for ~3 seconds and then the atmosphere crash screen.
@
CameronCataclysm:
@
Xdqwerty:
@
Xdqwerty:
