iOS 10 Public Beta - App crashes when logging weight

[alotufo]

I realize that iOS 10 is still in Beta, but I thought I would report this since I can't find it on these forums. Reporting it so it can be resolved for the iOS 10 final release.

When logging a new weight, the app crashes. After starting the app again, the weight is in fact logged. It's happened consistently for me for the last few days.

iOS 10 Public Beta 3.

[SunsetRunner]

easy

don't use Beta.

the problem is beta, not Fitbit app.

[bbarrera]

---

@SunsetRunner wrote:

the problem is beta, not Fitbit app.

---

Not so fast. It might be the Fitbit app, each new release of iOS and Android has changes to the APIs that the apps use. Thats the reason for reporting, in case its the Fitbit app that needs tweaking to work on the next OS version.

[alotufo]

---

@bbarrera wrote:

---

@SunsetRunner wrote:

the problem is beta, not Fitbit app.

---

Not so fast. It might be the Fitbit app, each new release of iOS and Android has changes to the APIs that the apps use. Thats the reason for reporting, in case its the Fitbit app that needs tweaking to work on the next OS version.

---

Exactly. This is the reason for reporting it. As a developer myself, saying not to use Beta doesn't help. I test lots of apps. Only the Fitbit developers will know whether this is a problem with the Fitbit app or with iOS 10 Beta.

[SunsetRunner]

---

@alotufo wrote:

---

@bbarrera wrote:

---

@SunsetRunner wrote:

the problem is beta, not Fitbit app.

---

Not so fast. It might be the Fitbit app, each new release of iOS and Android has changes to the APIs that the apps use. Thats the reason for reporting, in case its the Fitbit app that needs tweaking to work on the next OS version.

---

Exactly. This is the reason for reporting it. As a developer myself, saying not to use Beta doesn't help. I test lots of apps. Only the Fitbit developers will know whether this is a problem with the Fitbit app or with iOS 10 Beta.

---

the problem can be in the Fitbit app because the Apple beta is the problem

so Fitbit fix it, then Apple fix it, and Fibit must fix it again.

a waste of time and money.

[alotufo]

DubiosP, you seem to be missing the point about my bug report, and my post, so I will explain again.

The bug report was not intended to get a resolution from you or from the rest of the community. The bug report was intended for the developers of the Fitbit iOS app. I am fully aware that running the Fitbit iOS app under iOS 9 solves the problem, since I have been happily running it for several months without this issue I reported.

Whether or not the problem lies with iOS 10 Beta, or with the Fitbit app, I do not know. The reason for the post was to give the Fitbit iOS app developers a potential head start with any problems that arise from upgrading to iOS 10 before the launch. They can choose to address the problem and put out a fixed release, they can choose to gather all of the bug reports, work on them on a Fitbit iOS Beta version app of their own, or they can just choose to wait until the iOS 10 final version has been released and then release a new iOS app version. Of course, as users of their products and their apps, we would be more satisfied customers if they released a version of the Fitbit iOS app shortly after Apple releases iOS 10 rather than waiting for them to start working on the problems after iOS 10 final is released.

What you are proposing suggests that no one should upgrade to Beta software, and therefore no one should report any bugs they find to software developers. This means that users would then have to wait for the problems to be found, reported, tested by the developers and then wait for a release of a new app. This defeats the purpose of Apple releasing Developer and Public Beta versions. To find problems with software before the versions are final.

I hope this clears things up for you and that you can understand the reason for people to upgrade to Beta software, and to report potential issues to the software developers.

[bbarrera]

---

@SunsetRunner wrote:

the problem can be in the Fitbit app because the Apple beta is the problem

so Fitbit fix it, then Apple fix it, and Fibit must fix it again.

a waste of time and money.

---

When any company upgrades an OS, for example iOS, Android, Windows, or Mac OS X, there is a chance that apps must be upgraded.

The reason for a beta is for app developers like Fitbit to determine if they need to make changes, or if there is a bug to report to Apple/Google/Microsoft/etc.

[SunsetRunner]

i'm managing some iPhone, and my company manages thousand of them.

the company position, and i agree, is very clear : don't upgrade before we deliver a green light.

that's Apple responsability to not break the business

[alotufo]

---

@SunsetRunner wrote:

i'm managing some iPhone, and my company manages thousand of them.

the company position, and i agree, is very clear : don't upgrade before we deliver a green light.

---

A work environment is much different than a home environment, which is what this app is aimed for, but that does not make what you are saying correct. Beta testers report problems so that app developers can fix them before the release. The truth is that unless you are a Fitbit iOS app developer, you simply don't know whether the problem is with iOS 10 or with the Fitbit app.

If Apple releases iOS 10 and the app likely still crashes in this particular instance, are you going to still tell people to not upgrade to iOS 10? Are you going to tell Apple to change iOS 10 so that the Fitbit app works again?

[DerrickS]

@alotufo Thanks for the feedback! As stated earlier in this thread, iOS 10 is still a beta operating system, so it's possible that the final version of iOS 10 looks completely different from the beta version.

As a consequence, it is possible for iOS 10 beta users to have a sub-optimal experience like the one you are describing, but I'll be sure to pass this feedback along to our developers.

[bbarrera]

@DerrickS thanks for passing along.

@alotufo we've made our point, the simple reality is that all OS vendors release updates that can and do break compatibility with *some* apps. That's why one of the reasons for beta testing (that we've explained) is to allow app vendors plenty of time to react to changes that break features in an app. Another reason given by @SunsetRunner is for IT to say no, as its their job to support users and not beta testers. I think its time to move on.

[alotufo]

---

@bbarrera wrote:

@DerrickS thanks for passing along.

@alotufo we've made our point, the simple reality is that all OS vendors release updates that can and do break compatibility with *some* apps. That's why one of the reasons for beta testing (that we've explained) is to allow app vendors plenty of time to react to changes that break features in an app. Another reason given by @SunsetRunner is for IT to say no, as its their job to support users and not beta testers. I think its time to move on.

---

I agree. As a past IT Manager for several hundred users as well, I agree that staff should not be allowed to install whatever iOS version they wish, especially on company-owned equipment, as a properly managed IT department would centrally manage such devices anyways through third-party tools. But we are not talking about a work environment here, so the response and suggestion from DubiosP was not necessary.

[SunsetRunner]

This problem remains today with the public release version of iOS10. You log your weight..poof, the app crashes. You reopen the app and your new entry is present. I guess this means you can't blame it on beta lol. Stop adding new features and fix your bugs Fitbit!

[alotufo]

---

@SunsetRunner wrote:
This problem remains today with the public release version of iOS10. You log your weight..poof, the app crashes. You reopen the app and your new entry is present. I guess this means you can't blame it on beta lol. Stop adding new features and fix your bugs Fitbit!

---

Yup, something changed in iOS 10 that makes the Fitbit app crash when logging weight manually, and when I reported it I hoped that the devs at Fitbit were running iOS 10 Beta as well and would have it resolved for the final version, but I was wrong. iOS 10 has been released for almost two weeks and there's still no fix, even after a Fitbit iOS app update to version 2.27.

Personally, I gave up and bought an Apple Watch instead and will be selling my Blaze.