This is going to be a huge pain for support if you can't tell what version of the app you're running. iTunes helps, but it actually tells you what version is stored in iTunes, not what version is on the phone. There's an edge case there if the user hasn't synced since they downloaded an update in iTunes. I'd suggest adding this to the settings panel (right next to the custom server switch)
Moving FFHome-related bugs to new component -> Firefox Home
Component: Experimental Clients → Firefox Home
QA Contact: experimental.clients → firefox-home
Should be fixed in 1.0.2
How about http://stefan.arentz.ca/stuff/grabs/1281396624.png ... I have a patch ready.
Was already fixed in changeset b36ea5140a51
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
Verified fix on FF Home 1.0.2b3
I have double checked and all of my apps are up to date. I am running iOS 4.0. According to the app store 1.0.2 is the most recent version (and the one I should be running), but my about screen displays no version number. Screenshot to follow.
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
Created attachment 477173 [details] Screenshot of my About screen displaying no version number According to the update system I should be running version 1.0.2
Created attachment 477174 [details] 1.0.2 version screenshot Works for me. i'm on iOS 4.1. see screenshot
(In reply to comment #7) > Created attachment 477173 [details] > Screenshot of my About screen displaying no version number > > According to the update system I should be running version 1.0.2 See Settings > Firefox Home
I've closed this issue as the version number is not in the About screen but part of the settings that can be found in the built-in Settings.app.
Status: REOPENED → RESOLVED
Last Resolved: 9 years ago → 9 years ago
Resolution: --- → WONTFIX
actually the original bug was fixed, just fixed and verified in settings.app. if there is a need to add this to the home app, please file a separate bug.
Status: RESOLVED → VERIFIED
Resolution: WONTFIX → FIXED
You need to log in before you can comment on or make changes to this bug.