Closed LanWolf closed 8 months ago
Same issue here. Even when Smart Position is on, the location isn’t being updated at all when moving or even when standing still on a new location. The position log is sporadic being updated, it mostly waits for the set interval. But when de app isn’t active at that time, the location is not updated. Also when you entirely close the app (from the active apps list) and reopen it, the location is not being updated (this was working before).
Same here after updating IOS App, location stuck
Me too 2.2.23 beta, IoS app vrsion 2.2.26 (1)
I thought I was loosing my mind, same here. Location not updated on new node from iOS app no matter what settings I change. Running latest beta firmware (2.2.23) and iOS app up-to date.
EDIT: I had 2 nodes connected to the same iOS device and then I switch between devices the share location with the app settings turns off sharing location each time.
Same on 2.2.22 here. Viewing the Bluetooth-connected node log shows new events but with stale coordinates.
Curiously, Settings > Route Recorder does appear to update.
I am running a T-Lora T3 V1.6.1 running Firmware 2.2.21. iOS client version 2.2.26(1). I am seeing something similar. What I have set is, under "App Settings" I have "Share location" and Smart position" both on. Under "Position Config" I also have "Smart Position" on. Under iOS settings for the Meshtastic app, "Location" I have it set to "Always". Also I keep the app running at all times.
App version 2.2.26, Heltec v3 firmware 2.2.19 - also getting the same problem. Location was working, but has now stopped.
DIY 2.2.22 Latest IOS Map Not Working Nodes do not show Node Map, Position Log Pax Counter has no idea where it send I can only send messages for now
Me too! Heltec V3 IOS app ver. 2.2.26 FW ver. Same results after trying 2.2.21, 2.2.22 & 2.2.23 Seems like it all started with one of the recent IOS Meshtastic app updates.
I have (2) Rak Wireless WisBlock boards and use an iPhone running the latest iOS 17.3.1 operating system. My WisBlock's don't have GPS, so up through around the afternoon on March 1, 2023, my WisBlocks were getting the GPS from my phone through the Meshtastic APP. Sometime around Friday evening, my WisBlocks no longer get GPS from my phone through the Meshtastic APP. I have updated the Mestastic APP to the latest version with no improvement. As others have mentioned, in the Meshtastic APP, when I select my node device, the 'Node Map' and 'Position Log' are greyed out. Clicking on 'Mesh Map', I just get a view of the world map and no marker for my node is showing up. However, when I go to 'App Settings' in the Meshtastic APP, and scroll down to 'Phone GPS', I see the GPS Coordinates are updating live in the APP. Additionally, when I select 'Route Recorder' in the Meshtastic APP Settings menu, I see a map and can zoom in and it shows a blue dot corresponding to my GPS coordinates and if I walk around with my phone, I can see the dot moving around the map. So, it seems that the Meshtastic APP is accessing my GPS location from my iPhone properly, but the Meshtastic APP is not utilizing it in the Node Map, Position Log and Mesh Map.
I appreciate Meshtastic is open source but would be helpful to get some developer engagement on GitHub even if it’s just to acknowledge this is going worked on.
I appreciate Meshtastic is open source but would be helpful to get some developer engagement on GitHub even if it’s just to acknowledge this is going worked on.
There's primarily a single developer that handles the Apple applications. It's important to remember that all of our developers volunteer their time. They're not going to be able to instantly respond to every issue/request. As soon as they're able to fix this, they will. In the meantime I could suggest downgrading to an earlier version until it is fixed.
I appreciate Meshtastic is open source but would be helpful to get some developer engagement on GitHub even if it’s just to acknowledge this is going worked on.
There's primarily a single developer that handles the Apple applications. It's important to remember that all of our developers volunteer their time. They're not going to be able to instantly respond to every issue/request. As soon as they're able to fix this, they will. In the meantime I could suggest downgrading to an earlier version until it is fixed.
We would love to downgrade but apple won’t let us. If you can roll back the version from app store it’s better
I appreciate Meshtastic is open source but would be helpful to get some developer engagement on GitHub even if it’s just to acknowledge this is going worked on.
There's primarily a single developer that handles the Apple applications. It's important to remember that all of our developers volunteer their time. They're not going to be able to instantly respond to every issue/request. As soon as they're able to fix this, they will. In the meantime I could suggest downgrading to an earlier version until it is fixed.
We would love to downgrade but apple won’t let us. If you can roll back the version from app store it’s better
Fair point. You'll have to wait for the fix then unless you have an Android device or a Meshtastic device with built-in GPS.
I appreciate Meshtastic is open source but would be helpful to get some developer engagement on GitHub even if it’s just to acknowledge this is going worked on.
There's primarily a single developer that handles the Apple applications. It's important to remember that all of our developers volunteer their time. They're not going to be able to instantly respond to every issue/request. As soon as they're able to fix this, they will. In the meantime I could suggest downgrading to an earlier version until it is fixed.
sadly, on iOS you cannot downgrade, so we are stuck with this big issue until it is fixed..
altough I really respect the voluntary part, I would also expect a certain commitment.
And a big bug like this without any response in days ? That leaves me with some questions about this project’s development continuity in the future.
If the current dev stops, meshtatsic just stops for iOS users ?
there are many people buying (expensive) hardware use this software and then they will be left in the cold with non working devices ?
That makes me feel worried.
I appreciate Meshtastic is open source but would be helpful to get some developer engagement on GitHub even if it’s just to acknowledge this is going worked on.
There's primarily a single developer that handles the Apple applications. It's important to remember that all of our developers volunteer their time. They're not going to be able to instantly respond to every issue/request. As soon as they're able to fix this, they will. In the meantime I could suggest downgrading to an earlier version until it is fixed.
sadly, on iOS you cannot downgrade, so we are stuck with this big issue until it is fixed..
altough I really respect the voluntary part, I would also expect a certain commitment. And a big bug like this without any response in days ? That leaves me with some questions about this project’s development continuity in the future. If the current dev stops, meshtatsic just stops for iOS users ? there are many people buying (expensive) hardware use this software and then they will be left in the cold with non working devices ? That makes me feel worried.
This is a free project that you have chosen to use, and as stated before maintained by the generous free time and effort by volunteers. You have also volunteered yourself to use it, free of charge, and free of any obligation to help maintain or enhance it. There is no commitment that anyone owes anyone else here.
Edit: we also only have a single maintainer for the Android app, so if anyone would like to volunteer their time and expertise to maintain either of these apps please do so we're not limited to the kindness of two people to sustain everything app-related.
altough I really respect the voluntary part, I would also expect a certain commitment.
I would say they're pretty committed. But that's just my opinion.
And a big bug like this without any response in days ? That leaves me with some questions about this project’s development continuity in the future.
We're talking 3 days. For free software. I don't think we need to get dramatic about this. It's inconvenient, I get that. But also things happen. It'll get fixed soon. Do you have an android device you can use in the interim? Or how about a device with GPS built-in. It's smart to have backups.
An open source, **off-grid**, decentralized, mesh network built to run on affordable, low-power devices
If the current dev stops, meshtatsic just stops for iOS users ? there are many people buying (expensive) hardware use this software and then they will be left in the cold with non working devices ?
Basically. Unless others start to pitch in and help? Know any SwiftUI developers? Let them know. It's hard to find developers not only skilled enough but also willing to work for free.
That makes me feel worried.
I don't think you need to worry right now, it'll be okay.
altough I really respect the voluntary part, I would also expect a certain commitment. And a big bug like this without any response in days ? That leaves me with some questions about this project’s development continuity in the future. If the current dev stops, meshtatsic just stops for iOS users ? there are many people buying (expensive) hardware use this software and then they will be left in the cold with non working devices ? That makes me feel worried.
All the code is online so unlike when google etc pull the plug on projects, anyone can keep this project going.
I will try to find the cause of the issue. Yesterday I made it so I was able to push the code to my iPhone so I can test any changes I make. Probably has something to do with the newer changes so will look through those.
I will try to find the cause of the issue. Yesterday I made it so I was able to push the code to my iPhone so I can test any changes I make. Probably has something to do with the newer changes so will look through those.
First of all regardless of what the others said, thank you so much for putting your experience into this app. Second yes I think it’s regarding the last changes and updates. Last connect I had with the node was 27-03-2024 that the last date location was working. Lastly, just calm angry people down is there a way to rollback to older versions?
I wish we could it ourselves but Apple doesn’t allow to install older version.
Thank you for checking into the iPhone Meshtastic App GPS problem Benjamin!
I will try to find the cause of the issue. Yesterday I made it so I was able to push the code to my iPhone so I can test any changes I make. Probably has something to do with the newer changes so will look through those.
Pretty sure the issue is actually "resolved" in the TestFlight build. It's just the Apple Store that seems to have the issue. I imagine we can expect an update there as soon as Garth is able to.
I will try to find the cause of the issue. Yesterday I made it so I was able to push the code to my iPhone so I can test any changes I make. Probably has something to do with the newer changes so will look through those.
Pretty sure the issue is actually "resolved" in the TestFlight build. It's just the Apple Store that seems to have the issue. I imagine we can expect an update there as soon as Garth is able to.
Where I can find the test flight link?
I will try to find the cause of the issue. Yesterday I made it so I was able to push the code to my iPhone so I can test any changes I make. Probably has something to do with the newer changes so will look through those.
First of all regardless of what the others said, thank you so much for putting your experience into this app. Second yes I think it’s regarding the last changes and updates. Last connect I had with the node was 27-03-2024 that the last date location was working. Lastly, just calm angry people down is there a way to rollback to older versions?
I wish we could it ourselves but Apple doesn’t allow to install older version.
I have only made one contribution to the iOS app before so I am not the one you should be thanking.
I will try to find the cause of the issue. Yesterday I made it so I was able to push the code to my iPhone so I can test any changes I make. Probably has something to do with the newer changes so will look through those.
Pretty sure the issue is actually "resolved" in the TestFlight build. It's just the Apple Store that seems to have the issue. I imagine we can expect an update there as soon as Garth is able to.
Where I can find the test flight link?
It's not a public TestFlight, you have to ask to be added. You can ask in the #Apple channel on discord and Garth will let you know how.
This issue has been mentioned on Meshtastic. There might be relevant details there:
https://meshtastic.discourse.group/t/position-greyed-out/10899/4
I can only comment on my own experience and situation but the latest TestFlight version of the app solved the GPS issue for me. It’s worth pointing out that there has been no change to the GPS code so your mileage may vary.
The TestFlight version has now been released in the AppStore. Are people seeing the GPS issue fixed for them?
Seems fixed for me. I haven't been able to forward my phone's GPS to a new Heltec V3.
I upgraded the iOS app to 2.3.0 (842)
from the AppStore. Turned on "Smart Position" again and now see a proper fix and Position Log
from the Heltec V3 using my iPhone's GPS.
Thanks!
I upgraded to the lastest Meshtastic App in the Apple store this morning. I did not update the firmware on my WisBlock. From my very limited testing, the new Mestastic App does once again appear to be properly allowing my WisBlock without built-in GPS to retrieve the GPS location coordinates from by iPhone. Big thank you to Garth Vanderhouwen and the rest of the Meshtastic team for getting this issue straightened out!
The TestFlight version has now been released in the AppStore. Are people seeing the GPS issue fixed for them?
Works like a charm. THX
Firmware Version
2.2.23
What did you do?
I disabled gps pass thru in the app setting a few miles before I got home last Thursday to prevent the gps expose my home location.
After updating the app to 2.2.25 and later to 2.2.26 (1) Friday, today Saturday I re-enabled gps pass thru after drivig a few miles, but t keeps sending the last location from Thursday.
Restarting the device and phone did not help. Now it has no gps location, and does not transmit any location.
Expected Behavior
I would expect the gps to pick up when enabling pass thru in the app
Current Behavior
Does send no location or the last know location before updating the app.
Participation
Additional comments
Even went back to firmware form 2.2.24 to 2.2.23 to,check if it was fw related.