Acknowledged

bug: app trials documentation page has invalid example OR simulator bug

On this page: https://developer.garmin.com/connect-iq/core-topics/trial-apps/ there's an example manifest:

See in 1st comment, can't post here

however this example is invalid or probably more precisely misleading, because it won't work with any device that has minSdkVersion="1.3.1" (or greater), only with devices that have 2.3.0. If you add the iq:trialMode section to the manifest you can still compile it for older devices, for example fenix3, epix, but it will fail to start in the simulator:

Error: Symbol Not Found Error Details: Failed invoking <symbol> Stack:
Error: Symbol Not Found
Error Details: Failed invoking symbol
Stack:
Encountered app crash.

Another possibility is that the bug is not in the documentation and apps with iq:trialMode section in the manifest are supposed to work (without the trial feature, similar to how epix works if iq:uses-permission id="FitContributor" is in the manifest, even though it doesn't have fit) and the bug is in the simulator (at least in fenix3, epix)

Parents
  • Regarding using '<' and '>': I took another look at this before contacting IT, and I was able to include '<' and '>' in a bug report, both in the main block of text and in a code block (incidentally, identified as XML): https://forums.garmin.com/developer/connect-iq/i/bug-reports/test. Your initial report also includes these characters on the second line in the error message you included.

    I don't mean to suggest there's absolutely no problem, but it must be more nuanced than just being entirely unable to use those characters in the post. Let us know if you continue to run into this problem in the future.

Comment
  • Regarding using '<' and '>': I took another look at this before contacting IT, and I was able to include '<' and '>' in a bug report, both in the main block of text and in a code block (incidentally, identified as XML): https://forums.garmin.com/developer/connect-iq/i/bug-reports/test. Your initial report also includes these characters on the second line in the error message you included.

    I don't mean to suggest there's absolutely no problem, but it must be more nuanced than just being entirely unable to use those characters in the post. Let us know if you continue to run into this problem in the future.

Children
No Data