# Problems with Torch and SW Maps V1.3.0 (iOS) \[May 2026\]

**URL:** <https://community.sparkfun.com/t/problems-with-torch-and-sw-maps-v1-3-0-ios-may-2026/68729>\
**Category:** GPS/GNSS\
**Created:** [May 9, 2026, 9:39pm UTC](https://community.sparkfun.com/t/problems-with-torch-and-sw-maps-v1-3-0-ios-may-2026/68729 "2026-05-09T21:39:28Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![rftop](https://yyz1.discourse-cdn.com/sparkfun/user_avatar/community.sparkfun.com/rftop/32/6121_2.png) [@rftop](https://community.sparkfun.com/u/rftop)\
**Post date:** [May 9, 2026, 9:39pm UTC](https://community.sparkfun.com/t/problems-with-torch-and-sw-maps-v1-3-0-ios-may-2026/68729/1 "2026-05-09T21:39:28Z")

</div>

Torch on v3.3, UM980 firmware: 17548  
I cant get any SIV with SW Maps iOS V1.3.0 (latest).

I’ve re-flashed V3.3 firmware and reset to factory defaults.

Also, it gets mad about simple changes like requesting a 1Hz measurement rate :

 ![image](https://canada1.discourse-cdn.com/sparkfun/original/2X/7/78ccdd4a10b960db86dfdde6ceadd1b262e208f3.png)

But it turns out the Torch appears to be working fine for Android, after I spied on the NMEA with an Android Tablet. NMEA stream looks good. I then checked SW MAPS (Android) and everything is fine.

The Torch just appears dead with the latest iOS version of SW Maps. Same goes for iOS Diamond Maps, etc.

Has anyone else checked on the Torch (latest FW) with iOS ? Maybe it’s just my torch ?

---

<div class="post-metadata">

**Author:** ![rftop](https://yyz1.discourse-cdn.com/sparkfun/user_avatar/community.sparkfun.com/rftop/32/6121_2.png) [@rftop](https://community.sparkfun.com/u/rftop)\
**Post date:** [May 10, 2026, 12:15am UTC](https://community.sparkfun.com/t/problems-with-torch-and-sw-maps-v1-3-0-ios-may-2026/68729/2 "2026-05-10T00:15:48Z")

</div>

I was able to get SW Maps (iOS) to work after turning down the individual NMEA message  
rates.

Still not sure why I cant adjust the GNSS Receiver rate to 1Hz though.

 ![image](https://canada1.discourse-cdn.com/sparkfun/original/2X/2/2488c51a06276c87062eca8baf45b908bb3487d3.png)

---

<div class="post-metadata">

**Author:** ![PaulZC](https://yyz1.discourse-cdn.com/sparkfun/user_avatar/community.sparkfun.com/paulzc/32/67_2.png) [@PaulZC](https://community.sparkfun.com/u/PaulZC)\
**Post date:** [May 11, 2026, 12:41pm UTC](https://community.sparkfun.com/t/problems-with-torch-and-sw-maps-v1-3-0-ios-may-2026/68729/3 "2026-05-11T12:41:03Z")

</div>

Hi Ryan (@rftop ),

I will take a look at this next week, when I am back at my desk.

It looks like there may be an error in the way we are passing float to getNewSetting - which expects int. And / or a gremlin in fixRateIsAllowed.

Please create an issue for this on GitHub - so it doesn’t get forgotten.

Apologies for the inconvenience / delay,  
Paul