Details: "Could not find symbol '00800311'"

Actually, the manifest.xml in the .iq is different when it comes to min fw/min ciq on a device by device basis.  That's where the bug travis mentioned comes into play.

The proper function is that based on this, the user should be given a warning when they try to download that they need to update their FW before they can download but that's not happening the way it should..

@travis.connectiq - so if i export my app using a newer sdk version, it won't be compatible with the same devices it would be with an older sdk version, despite the same api spec in the manifest?  that seems wrong, as in broken not just looks.

ps. you guys do know that the forum doesn't let us post hardly ever, right? i can't reply to your comment and i can't even post a new comment without waiting "to post again" even though i haven't posted in days.

Thanks for confirming Travis.ConnectIQ!
This will no doubt save me debugging false positives from users.

Yes. We discovered (after my post above) that the App Store is letting devices get software that should not be allowed. I'm not sure what the timeline is on the fix, but I really hope it is soon. This makes us look really bad.

Hi folks, 

I've recently had a user report a similar issue where one of my watch faces would crash on their device, looking at the debug logs I'm seeing this exact error. My build of the watch face was using the 3.1.6 version of the SDK and the user was using the 3.8.0 Vivoactive 3.

---
Error: Symbol Not Found Error
Details: "Could not find symbol '00800311'"
Time: 2019-11-27T13:04:05Z
Part-Number: xxx
Firmware-Version: '3.80'
Language-Code: spa
ConnectIQ-Version: 3.1.6
Store-Id: d863efb4-4690-4ce0-b314-aaf59598d7a7
Store-Version: 37
Filename: 9BRC3527
Appname: Pipboy
Stack:
  - pc: 0x100025bb

I've redacted the part number as I wasn't sure if that was related to the user's device specifically.

For now, I've built a PRG for the user to sideload and test on their device using the 3.1.4 SDK to see if this rectifies the problem. However, I have a wider concern which is that according to Travis.ConnectIQ comment

> If you had uploaded the app to the store and tried to download it to your device, you would get a message that tells you that you need to update your device firmware. Since you're side-loading there is nothing to prevent you from doing this.

This doesn't seem to be true, on my end at least it looks like the user has managed to download a build of the watch face from the store which used an SDK that their device doesn't support. Building the watch face with an older SDK for a release to the store isn't ideal as it means I can't target newer devices (as far as I'm aware), but building with an SDK that ends up with the watch face crashing on certain devices isn't a great user experience :/

I see there's also a ticket attached to this thread so maybe there is work going on in the background to rectify these issues, but I just wanted to add my experience.