https://forums.garmin.com/developer/connect-iq/The central hub for the Connect IQ Developer Community.en-USTelligent Community 13https://forums.garmin.com/developer/connect-iq/f/showcase/435513/rucktrack-v2-rucking-hiking-weighted-vest-walks-on-garmin-amoled/2033185Fri, 22 May 2026 16:42:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:36117b88-17e1-4bb7-a5a6-d3f064e2934bMeridianv2.1 update. Three Connect-side wins since the v2.0 post above: Sessions now classify as Rucking in Garmin Connect, not Hike. Works on every supported watch via FIT subsport 124, not just the few that ship Garmin’s native Rucking activity (tactix 8, fēnix 8, FR 970, select Instinct). Per-second grade (%) and metabolic rate (W) write as FIT record fields, so the activity detail page in Connect renders them as time-series charts alongside the native pace / HR / elevation graphs. The post-save summary now ends with a Totals page showing lifetime ruck count, distance, time, and calories. Increments visibly each save. Plus polish: sessions auto-name with pack weight in the Connect activity list (e.g. “Ruck 35 lb”), start / pause / save / discard each play a short tone, and FR 70 is now in the supported list (57 devices total). OP edited to reflect current v2.1 state (six-page summary, Recent Updates rollup, device list, roadmap). Store: RuckTrack on Connect IQ — $2.99 USD Docs: https://meridian-apps.github.io/rucktrack-docs/https://forums.garmin.com/developer/connect-iq/f/connect-iq-web-store/433333/connect-iq-sales-dashboard/2033131Fri, 22 May 2026 14:45:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:2c5ccf7f-f325-4f5d-8d07-d3563571fe37Silvero StudiosHey! Pushed two PRs to your fork — kept them tight and independent so you can take one or both: #6 — Auto-detect currency from CSV github.com/.../6 The dashboard was hardcoding $ everywhere, which meant anyone paid in EUR/GBP/JPY/etc. saw the wrong symbol. This reads the Share Currency column from each row, figures out the dominant currency, and uses the right symbol in all the stats cards, axes, tooltips and forecasts. Covers ~25 ISO codes, falls back gracefully for any I missed. USD users see zero change. #7 — Optional Windows launcher github.com/.../7 Just a .bat + a PowerShell shortcut installer for Windows users who don't want to live in the terminal. Drop it if you'd rather keep the repo terminal-pure — no hard feelings. Both target your default branch. Happy to iterate on anythinghttps://forums.garmin.com/developer/connect-iq/f/connect-iq-web-store/433333/connect-iq-sales-dashboard/2033109Fri, 22 May 2026 13:48:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:b306280b-459f-451d-bf8b-c295e6d4ad98CharlieHello Silvero Studios , those sound like nice improvements The repo is at https://github.com/cdphx4/CIQ-Dash/pulls , if you fork it and open a pull request I can review the changes and merge it easily. Thank you for contributing!https://forums.garmin.com/developer/connect-iq/f/discussion/434798/cannot-access-developer-program-application-form-under-construction/2033080Fri, 22 May 2026 12:21:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:4b2bdacc-8958-4ded-b743-4217ce66a1e93064625I am also looking to integrate Garmin into my app. Currently, users can import their activities through the Health app, but because some don't use Apple Health or Health Connect, the only direct solution is to register as a Garmin Developer. Below is the official response I received from Garmin. Hopefully, they will complete their migration soon so we can integrate Garmin products directly into our apps: Thank you for reaching out and for your interest in the Garmin Connect Developer Program. The application form for new API access requests is currently unavailable while we complete updates to the Garmin Connect Developer Program. During this transition, new access requests are temporarily paused . Once the updated developer program and application process are finalized, the access request form will be made available again on our developer website. We appreciate your interest in working with Garmin, and thank you for your patience while these updates are completed.https://forums.garmin.com/developer/connect-iq/f/discussion/436729/group-option-in-the-settings-doesn-t-work-correctly-when-you-use-a-settings-with-date-format-only-on-physical-watch-correct-in-simulatorFri, 22 May 2026 09:15:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:7d511e90-855c-49f0-9408-348db3d2c258riedid74When in the settings, you use group option and when in this group you have a field of date format, the field display an error and you can't exit correctly the setting. It's appear only on physical watch but its good in simulator To reproduce the bug. Define a simple watch face with settings. and add 2 informations In the display with garmin connect on your phone , you can't see the correct date. and you can't save it because it's empty www.w3.org/.../XMLSchema-instance" xsi:noNamespaceSchemaLocation=" ">developer.garmin.com/.../resources.xsd"> 0x000000 0xFF0000 false 1798758000 www.w3.org/.../XMLSchema-instance" xsi:noNamespaceSchemaLocation=" ">developer.garmin.com/.../resources.xsd"> @Strings.ColorBlack @Strings.ColorDarkGray @Strings.ColorLightGray @Strings.ColorWhite @Strings.ColorBlack @Strings.ColorBlue @Strings.ColorRed @Strings.ColorWhitehttps://forums.garmin.com/developer/connect-iq/f/connect-iq-web-store/433333/connect-iq-sales-dashboard/2033041Fri, 22 May 2026 08:12:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:1929dfd4-7ad7-434d-9a5e-6b09fd16a86dSilvero StudiosHeyy, I gave this a small update, I made so you can compare 2 .csv sales reports, and also made sure you can see all of your apps sales numbers in the same place instead of the inicial top 4. Feel free to contact me I can give it to you so you can upload it to github! insta: silvero.studios email: hello@silverostudios.comhttps://forums.garmin.com/developer/connect-iq/f/showcase/436721/dare-to-benchmark-your-garmin-with-wristbench-real-app-side-performance-testingFri, 22 May 2026 02:17:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:3bca63d3-4058-4dc1-8f4d-1aa11d64f3b1li2niuI’m excited to share WristBench , a Connect IQ benchmark designed for Garmin watches. Unlike synthetic benchmarks, WristBench measures real-world application performance directly on your device. If you’ve ever wondered how your watch performs under actual Connect IQ workloads, this is for you. What WristBench Measures WristBench evaluates four core performance areas of your Garmin watch: Integer Logic Tests integer computation, array handling, loops, and sorting. Measures how efficiently your device processes typical app logic. VM Memory Behavior Evaluates string handling, object allocation, and garbage collection efficiency. Reflects real-world memory usage scenarios inside the Connect IQ VM. Local Storage I/O Measures read/write performance to the local storage on your watch. Captures the speed at which apps can store and retrieve data. 2D Rendering Stress-tests 2D graphics throughput and screen refresh. Shows how smoothly your watch can render complex displays. After the tests, WristBench calculates a total score for your watch. This score reflects practical app-side performance , not theoretical chip speed. Upload & Compare You can upload your results to the public leaderboard , which groups watches by model for fair comparison. Factors like firmware version, Connect IQ version, battery profile, screen type, resolution, and device temperature may slightly influence scores, so consider running multiple tests to see stable results. How to Get WristBench Search “WristBench” in the Connect IQ Store to download. Run the benchmark and upload your score. Compare with other Garmin users worldwide. For the leaderboard, methodology, and detailed whitepaper: https://benchmark.wristtale.comwristbenchbenchmarkconnectiqhttps://forums.garmin.com/developer/connect-iq/i/bug-reports/onhold-event-never-fires-near-the-12-o-clock-screen-edge-on-tactix-8-guessed-likely-conflict-with-system-touchscreen-lock-s-implementationThu, 21 May 2026 23:23:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:63a2c797-03dc-4d67-889e-96ad731d33539764157Spent a while debugging this — posting in case anyone else hit it or in case it's a known thing. On the device, onHold is never delivered when the touch lands near the top edge (~12 o'clock area). onTap at the exact same spot works fine. Simulator is unaffected — only the real device. Minimal repro: function onTap(evt) { System.println("tap " + evt.getCoordinates()); return true; } function onHold(evt) { System.println("hold " + evt.getCoordinates()); return true; } Tap top edge → tap line prints. Long-press top edge → nothing. Move 20-30px down, long-press works. My guess: the system's "long-press top of screen to lock touchscreen" gesture lives in the same area, so the firmware withholds the touch-down from CIQ until it decides whether it's the system gesture — and apparently never resolves to forwarding it as onHold. Short taps aren't ambiguous so they get through. If this is intentional, can it get documented? Or is there a way to opt out (something like "my view wants all touches, don't run system gestures")? Right now any radial/sector-style UI with a long-press "up" direction silently doesn't work on this hardware and the simulator gives no warning. Anyone else seeing this, or know a workaround other than "just don't put hold targets near the top"? what a buggy platformhttps://forums.garmin.com/developer/connect-iq/f/discussion/436700/getting-gyroscope-data-is-not-working-fr255sThu, 21 May 2026 17:56:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:c7697ea2-cace-4aca-b1a8-a7d388b5a2ceStanislav AndreevHello, I am using the most recent SDK (9.1.0). Also I got source of RawLogger application and rebuilt it. It does have gyroscope and I added its support in analogous way as accelerometer data retrieving implemented. Changed manifest to use API 5.0.0 (System 7) to make sure that fr255s will support gyroscope. Physically fr255s has gyroscope. Using real device. But gyroscope data empty. So the questions: 1. is gyroscope available on fr255s or firmware somehow prevents accessing its data (for external app like RawLogger)? 2. is there any possible way to get gyroscope data on fr255s real device? P. S. fr255s firmware version is 27.09 I'll be grateful for any information or advices.gyroscopehttps://forums.garmin.com/developer/connect-iq/i/bug-reports/merchant-onboarding-stuck-on-action-required-legal-disclosures-section-shows-no-signature-fieldThu, 21 May 2026 15:25:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:dbc49e86-d5a3-43b3-8bba-90b7e08de492RunLabsHi, I completed the merchant onboarding process 4 days ago. Personal details and bank account both show as Verified in Adyen, but the legal disclosures section renders with no checkbox or signature button — just the legal text. There’s no way to complete that step. As a result, the dashboard shows “Action Required” with nothing actionable to do. I’ve tried different browsers and incognito mode with no change. Has anyone else hit this? Is there a fix, or does this need to be resolved manually on Garmin’s end? ThanksConnect IQ Developersconnectiqmerchanthttps://forums.garmin.com/developer/connect-iq/f/discussion/436226/connect-developer-program-access-form-unavailable-anyone-got-through-recently/2032918Thu, 21 May 2026 14:12:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:ea180eaa-bf84-4246-8357-287f794f6b0d9311735Quick update for anyone landing here from search: I went through the Developer Contact Us form instead of the standard support email, and got an official reply within 5 hours. The official answer: new access requests are temporarily paused while Garmin updates the Connect Developer Program. No timeline given. They said the access form will be reopened once the new process is finalized. So the form being on "Stay tuned" is intentional, not a bug. If you're stuck like I was, use the Developer Contact form to at least get a ticket open and confirm you're in the system. Doesn't unlock access today, but it's better than the void. Hope this helps the next dev.https://forums.garmin.com/developer/connect-iq/i/bug-reports/connect-iq-ondrag-events-degrade-severely-under-continuous-dragThu, 21 May 2026 01:50:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:105fac81-8bd1-4b81-980b-54d0a0d37c509764157Test conditions on real tactix 8: minimal view, black background, one rectangle that snaps to the finger position in onDragging. No bitmap blits, no scene graph, no math — drawContent is effectively empty. Measured behavior First second or two: events arrive at ~15 Hz (~60–80 ms apart) After sustained drag, the rate progressively collapses By the end I could spin my finger in circles on the glass and the rectangle would update once every ~2 seconds The render frame is well under 16 ms — there is no possible app-side bottleneck here. The control case The native Garmin menu/list UI on the same device does not exhibit this. Scrolling is smooth and responsive throughout. So the touch hardware is clearly capable of delivering high-rate input; Connect IQ apps are not getting it. Ask This isn't a performance optimization issue I can work around with smaller bitmaps or fewer draw calls. It looks like a CIQ runtime issue (event queue starvation? thread starvation? touch-driver throttling specifically for CIQ apps?). Can someone from the CIQ team comment on whether this is known and whether app developers have any control?https://forums.garmin.com/developer/connect-iq/f/discussion/2213/pressing-buttons-in-simulator/2032772Wed, 20 May 2026 21:49:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:a55cdd0a-71f1-45e8-9f00-6c8f29e331c6Mattijah10 fcking years later and this still ain't working reliably lmao. At least keyboard buttons arehttps://forums.garmin.com/developer/connect-iq/f/showcase/436558/app-calimaster-pro---calisthenics-street-lifting-app-with-web-integration/2032689Wed, 20 May 2026 17:13:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:2b550c7a-0290-4840-9e0b-8b78138d394aGiovanni.CaliMasterPro#### Reserved for Changeloghttps://forums.garmin.com/developer/connect-iq/i/bug-reports/ambient-light-sensor-api-5-years-3-threads-still-no-access-time-to-unlock-modern-garmin-displaysWed, 20 May 2026 15:31:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:b5d571c6-06ef-4f0d-8bf1-75d61f45aafcalexandre.fournierHi Garmin team, I'm opening this ticket to consolidate a request that keeps resurfacing across the developer community. The ambient light sensor is physically present in nearly every modern Garmin watch, yet Connect IQ developers still have no way to read it. This isn't a one-off request. It's been raised at least three separate times, by different developers, over more than five years: - CIQQA-387 (Sept 2020, by an Edge 530 user) — closed June 2022 by @Brad.ConnectIQ with: *"Not planned for the Edge 530, but could be implemented for future devices."* - CIQQA-3639 — Ambient light sensor API access — try again" (Nov 2025, by @Dan for the Edge 840). Currently *Acknowledged*. Supported by @juliatuttle, @bin101, and myself. - "Edge Ambient Light Sensor reading" discussion thread (Jan–Feb 2026, by @jamie-web) — 17 subscribers actively looking for a workaround that doesn't exist. Many generations of "future devices" have shipped since 2022 (Instinct Crossover, Instinct 3, Fenix 8, Epix, tactix 8, Edge 840/1040/1050, Forerunner 965/970, Venu 3, Vivoactive 6) all with the sensor, none with API access. Why this matters strategically for Garmin Garmin has invested heavily in beautiful AMOLED and MIP displays across the lineup. Marketing emphasizes screen quality, outdoor readability, and adaptive backlight. But Connect IQ developers can't write a single watch face or data field that actually adapts to the lighting conditions the device is sitting in. If Garmin wants a developer community that uses the full potential of these modern displays, this sensor needs to be accessible. Right now, every third-party watch face renders identically at noon in direct sunlight and at 2am in bed, while the hardware is fully capable of doing better. Apple Watch and Wear OS both expose this. Garmin shouldn't be the one falling behind on a feature whose data is already inside the device. The simplest possible implementation I am far from having the expertise that you have Garmin. Maybe I am oversimplifying but... I would see this as an easy fix. No new hardware. No new permissions UI. No breaking changes. One method: ``` Toybox.Sensor.getAmbientLight() → Number ``` Read-only. Polled in `onUpdate()` — no callbacks needed. Return whatever's convenient for the firmware team: - Raw lux value, or - A normalized 0–100 scale, or - A 3-level enum: `DARK` / `MEDIUM` / `BRIGHT` Any of those three formats unlocks the use cases below. The 3-level enum is probably the lowest-effort path — it's essentially the same signal the firmware already computes for the backlight curve. What developers would be able to do with it - Adaptive-contrast watch faces (bright/high-contrast in sun, soft/dimmed indoors) - True day/night layout switching (driven by actual light, not just clock time or sunset tables) - Data fields that simplify themselves in low light to reduce visual noise - Bike light automation (the Smart Bike Lights community has been blocked on this for years) - Battery-saving logic (skip animation cycles when the user can't see them anyway) The ask , @ Brad.ConnectIQ — given that the 2022 "future devices" promise now applies to nearly the entire current lineup, can the Connect IQ team formally re-scope this? Even a coarse 3-level enum on System 8 devices would be a meaningful step forward and wouldn't require lux calibration work. To the community and anyone else who's been blocked by this: please drop a comment or here so this request is visible as the cross-thread, multi-year demand it actually is. Garmin tracks engagement on these tickets, and this is the moment to consolidate the signal. Thanks for considering.Connect IQ DevelopersAmbiant light APIuser experienceapioptimizationCIQConnect IQhttps://forums.garmin.com/developer/connect-iq/f/showcase/4247/watchface-urtime-moonphase/2032594Wed, 20 May 2026 12:13:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:ca4c6cee-daa3-418b-b589-be6d183973368049089Is there any way you update this to be available for Venu 4 (41mm). Please, it’s so pretty I have to have ithttps://forums.garmin.com/developer/connect-iq/f/discussion/436603/app-highlights---is-there-a-defined-process-for-getting-your-app-promoted-there-perhaps-a-form-or-an-emailWed, 20 May 2026 10:29:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:1eb5ea1c-a046-431e-b758-c0055ce6a5fb4292966I would like to understand how Garmin decides which apps to feature and which not, or how to draw Garmin's attention to its program.storehowtoConnect IQwatch apphttps://forums.garmin.com/developer/connect-iq/f/showcase/435208/water-tracker-pro-smart-hydration-for-your-garmin/2032573Wed, 20 May 2026 09:53:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:1e40d4c8-fe90-40ec-99a8-acea9fbf8c187620621how did u access dehydration info or how did u estimated sweat?https://forums.garmin.com/developer/connect-iq/f/showcase/369746/hate-this-new-format/2032568Wed, 20 May 2026 09:13:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:44f97640-1260-4973-b231-9164d20a70149499555I think the app’s interface is quite confusing and outdated stickman hook . Cheaper brands often provide a much cleaner experience. The scale section especially feels incomplete since it only shows raw numbers instead of detailed charts or analytics. For a €200 product, that’s a bit embarrassing.https://forums.garmin.com/developer/connect-iq/f/showcase/436248/watchface-linea-gear-up-get-out-look-sharp/2032565Wed, 20 May 2026 08:52:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:d30cafde-f4b5-4d09-b49c-2e8712f0dc1bCrafted.by.MiesChris thanks so much for your nice comment! Really appreciate that. Please consider also leaving a review in the Garmin IQ Connect Store, this will help others to find this watch face as well Link: apps.garmin.com/.../204a4a91-2be5-4131-8ce5-c0c5bfd36ac4