OB1 app "Bug" reports ONLY

  • HTML tutorial

Michael

Rank IX
Staff member
Founder 500
Member

Benefactor

15,584
Auburn, California, United States
First Name
Michael
Last Name
Murguia
Member #

0000

Ham/GMRS Callsign
KM6YSL
Thanks @Michael - let me know if I can do anything to help you pinpoint the issue. I will say, it started only AFTER I got approved for the new access. This could have been due to an update to the app or access level change.
This should be fixed in the new release (live now).would be great to hear your experience now.
 

trail_runn4r

US Rocky Mtn. Local Expert. Colorado: Denver Area
Member

Pathfinder III

4,815
Denver, CO, USA
First Name
Carlo
Last Name
Donzelli
Member #

16845

Not sure this has been reported already but from what I remember tapping on a notification to open a message never worked properly.
At the beginning after tapping the app would open to the first message to the thread. Now the app opens to the correct page of the thread.

At least for me on iOS 15, this is still broken, the app should open to the right thread, right page, right message.

Thank you!
OK - an extremely problematic issue for some users. Since it is not consistent (i dont have the issue) its been difficult to track down. Any specifics that might help would be greatly appreciated - one test - if you see a push note - wait 3 minutes, then tap it and see if it works. That would indicate we might have a race condition in the system and would be helpful to know. Thank you!
Just tried now, waited 5 minutes.
It took me to the last message of the thread, but it should have taken me to your reply instead.

Why do you thinks it’s a race condition?
The push notification payload should contain the id of the message that it should point too. Then, when tapping the notification your should trigger a deep link with that id as parameter.

Or at least this is how I think it should work

Edit: now that I sent this reply, the app still points to the last message before mine. It should probably focus on the last message instead (my reply)

Edit #2 (writing from web): from the app, I edited my message and saved, saved was successful because I can see the changes for web, but the app is frozen, stuck on my original message before my 1st edit. (new bug if no one else filed already)

Edit #3 (lol): Ok I figured this out, the app is not frozen, but after tapping "read more" it looks like I am on a different page, which shows my full message (without the edit though) but I can't scroll up and down to previous messages in the thread. If I tap back, I got back to the thread page.

Imho this UX is confusing. The 'Read More' button looks like it will expand the message in the current page but instead it just opens a new page. That would be more clear to the user if after tapping read more the app would present the new screen with a modal or push presentation style. If the screen immediately appears, it looks weird.
 
Last edited:
  • Like
Reactions: Michael

Z Adventures

Rank VI
Member
Investor

Pathfinder III

2,980
Georgia, United States
First Name
Mark
Last Name
Zeilenga
Member #

30262

This should be fixed in the new release (live now).
The issue with the Android Go Back button seems to be OK now. There are now places where that button doesn't do anything and places where it does. But at least it's not locking up. I can get used to when it works and when it doesn't.
 
  • Like
Reactions: Michael

Michael

Rank IX
Staff member
Founder 500
Member

Benefactor

15,584
Auburn, California, United States
First Name
Michael
Last Name
Murguia
Member #

0000

Ham/GMRS Callsign
KM6YSL
Just tried now, waited 5 minutes.
It took me to the last message of the thread, but it should have taken me to your reply instead.

Why do you thinks it’s a race condition?
The push notification payload should contain the id of the message that it should point too. Then, when tapping the notification your should trigger a deep link with that id as parameter.

Or at least this is how I think it should work

Edit: now that I sent this reply, the app still points to the last message before mine. It should probably focus on the last message instead (my reply)

Edit #2 (writing from web): from the app, I edited my message and saved, saved was successful because I can see the changes for web, but the app is frozen, stuck on my original message before my 1st edit. (new bug if no one else filed already)

Edit #3 (lol): Ok I figured this out, the app is not frozen, but after tapping "read more" it looks like I am on a different page, which shows my full message (without the edit though) but I can't scroll up and down to previous messages in the thread. If I tap back, I got back to the thread page.

Imho this UX is confusing. The 'Read More' button looks like it will expand the message in the current page but instead it just opens a new page. That would be more clear to the user if after tapping read more the app would present the new screen with a modal or push presentation style. If the screen immediately appears, it looks weird.
Agree on confusing UI. Push note: copy. Not exactly how it works because React Native, but it's something we are looking to improve soon.
 
  • Like
Reactions: trail_runn4r

trail_runn4r

US Rocky Mtn. Local Expert. Colorado: Denver Area
Member

Pathfinder III

4,815
Denver, CO, USA
First Name
Carlo
Last Name
Donzelli
Member #

16845

Agree on confusing UI. Push note: copy. Not exactly how it works because React Native, but it's something we are looking to improve soon.
Thanks! I think more in general one of the drawbacks to develop in ReactNative is that you lose the look and feel of the specific iOS / Android platform. Both type of users are used to their ecosystem and this being an hybrid app lacks of that customization. Whatever you can do to make the app feel more at home on iOS and Android will be really appreciated!
 
  • Like
Reactions: Michael

SJ.Overland

Rank VII
Member

Trail Blazer I

6,140
Beavercreek, OH, USA
First Name
Shaun
Last Name
Johannes
Member #

15310

Ham/GMRS Callsign
KE8TDZ
I've had a couple issues with track recording.
After a pause and resume my track did not resume recording, even though I did hit resume and the app showed the recording status icon. Also I noticed that my path was not showing up until I paused again. I just assumed that it was recording, but it wasn't showing the track for some reason. However after continuing on about another 30 miles and then ending for the day. I found that the track stopped recording near the last pause.


This was on iOS and the 2nd most recent release 11.7.0


Edit: here’s a link to the recording - KAT segment
 
Last edited:
  • Like
Reactions: Michael

Michael

Rank IX
Staff member
Founder 500
Member

Benefactor

15,584
Auburn, California, United States
First Name
Michael
Last Name
Murguia
Member #

0000

Ham/GMRS Callsign
KM6YSL
I've had a couple issues with track recording.
After a pause and resume my track did not resume recording, even though I did hit resume and the app showed the recording status icon. Also I noticed that my path was not showing up until I paused again. I just assumed that it was recording, but it wasn't showing the track for some reason. However after continuing on about another 30 miles and then ending for the day. I found that the track stopped recording near the last pause.


This was on iOS and the 2nd most recent release 11.7.0


Edit: here’s a link to the recording - KAT segment
This is very helpful. i am sorry your recording was compromised. I'll provide this info to the developers. It's unclear if this is an error with code or a UI error - meaning - we are not conveying record vs pause status clearly enough. Will look into this.
 

SJ.Overland

Rank VII
Member

Trail Blazer I

6,140
Beavercreek, OH, USA
First Name
Shaun
Last Name
Johannes
Member #

15310

Ham/GMRS Callsign
KE8TDZ
This is very helpful. i am sorry your recording was compromised. I'll provide this info to the developers. It's unclear if this is an error with code or a UI error - meaning - we are not conveying record vs pause status clearly enough. Will look into this.
It's no worries. I'm going to be doing another recording this weekend. So I'll try to snag a video of the error then of when I pause. It was kinda odd that when I paused the second time, all of the tracks that occur after the first resume appeared all of the sudden.
 

Scott_Milk

Rank IV
Launch Member

Explorer I

1,383
Rotorua, Bay of Plenty, New Zealand
First Name
Jacob
Last Name
Kelley
Member #

25260

Not sure it's a bug but it's kinda a problem. Whenever I try to change the layers on the map, it tells me to upgrade. I was grandfathered in by being a member before whatever the cutoff date was. As I understand it, there are still some features you HAVE to pay for with subscription. That's fine but the problem is that the BLM and I believe National Forrest lands layers are stuck on. I can't even see what layers because as soon as I hit the layers button it just tells me to upgrade. I used to be able to select layers before whatever update broke it so it seems dumb I can't now
 
  • Like
Reactions: Steve_ohhhhh

Steve_ohhhhh

Local Expert, QLD Australia
Member

Influencer I

4,178
Redbank Queensland, Australia
First Name
Steven
Last Name
Jappe
Member #

13609

Not sure it's a bug but it's kinda a problem. Whenever I try to change the layers on the map, it tells me to upgrade. I was grandfathered in by being a member before whatever the cutoff date was. As I understand it, there are still some features you HAVE to pay for with subscription. That's fine but the problem is that the BLM and I believe National Forrest lands layers are stuck on. I can't even see what layers because as soon as I hit the layers button it just tells me to upgrade. I used to be able to select layers before whatever update broke it so it seems dumb I can't now
I've noticed this issue too. Just been waiting to see if it got picked up by the powers that be.
 
  • Like
Reactions: Scott_Milk

SJ.Overland

Rank VII
Member

Trail Blazer I

6,140
Beavercreek, OH, USA
First Name
Shaun
Last Name
Johannes
Member #

15310

Ham/GMRS Callsign
KE8TDZ
Slight bug regarding importing GPX files. Every time I import a track, If i select Private on the initial creation it does not save that tag. It requires me to edit the trail and make it private a second time before the private tag is applied properly.
 

jwright

Rank VI
Member

Steward I

4,363
Lancaster, PA, USA
First Name
John
Last Name
Wright
Member #

28051

Unclear if a bug exists or it is user error. My OB1 app is showing 1 unread message, but will not clear even after reading all recent messages again, closing the app, and even rebooting the phone. The app has is up to date. Thanks
 
  • Like
Reactions: SJ.Overland

SJ.Overland

Rank VII
Member

Trail Blazer I

6,140
Beavercreek, OH, USA
First Name
Shaun
Last Name
Johannes
Member #

15310

Ham/GMRS Callsign
KE8TDZ
Unclear if a bug exists or it is user error. My OB1 app is showing 1 unread message, but will not clear even after reading all recent messages again, closing the app, and even rebooting the phone. The app has is up to date. Thanks
I have this same bug, It appeared yesterday.
 
  • Like
Reactions: jwright

Michael

Rank IX
Staff member
Founder 500
Member

Benefactor

15,584
Auburn, California, United States
First Name
Michael
Last Name
Murguia
Member #

0000

Ham/GMRS Callsign
KM6YSL
Not sure it's a bug but it's kinda a problem. Whenever I try to change the layers on the map, it tells me to upgrade. I was grandfathered in by being a member before whatever the cutoff date was. As I understand it, there are still some features you HAVE to pay for with subscription. That's fine but the problem is that the BLM and I believe National Forrest lands layers are stuck on. I can't even see what layers because as soon as I hit the layers button it just tells me to upgrade. I used to be able to select layers before whatever update broke it so it seems dumb I can't now
Hi Scott and @Steve_ohhhhh this issue has been resolved. PLease let me know if you have any issues with filters now.

M
 
  • Like
Reactions: Steve_ohhhhh