I'm sorry but sending custom headers like "x-ha-access" is not possible at the moment. The only supported auth method currently supported is basic access authentication.
The whole app settings logic is a part made by Garmin. As a developer, I do not have any influence on this part of the app/widget.
What I experienced:
As long as the widget is newly installed or updated, I can safe app settings using my iOS device. As soon as I safed app settings using my desktop version of garmin connect once the connection between iOS and the devices app settings (fenix3 in my case) is permanently broken.
In other words, if I use garmin connect on my win10 desktop once to write app settings, I can not witch to the smartphone app anymore. (because of the access denied bug) I have no idea why!
I copied the settings in the widget and it works. sort of. I mean the device does turn On but then a big IQ with an exclamation mark shows on the screen.
Any idea what am i doing wrong? My device is a Fenix 5.
Garmin describes how the device is logging crashes like this one. You could help me if you send me the log file. You would have to connect your watch using the USB cable and browse the file system on your whatch.
[h=2]Handling Crashes [/h]Despite the best debugging efforts, crashes will sometimes happen. There are two general types of on-device crash that can occur related to Connect IQ, which each generate log files: app crashes and device crashes.
[h=3]App Crashes[/h]App crashes typically result in an app quitting unexpectedly or displaying an ‘IQ!’ icon, but does not cause the entire device to crash or reboot. This kind of crash is most commonly due to a bug in an app, though it can also be due to a bug in Connect IQ itself. Whenever an app crash occurs, a CIQ_LOG.txt file is written or updated to /GARMIN/APPS/LOGS on the device, and contains information related to the crash that app developers may use to address the problem.
I you could send me this file to mail(at)sten-uhlig(dot)de
