Bowlr Status

[Resolved] Google database failures

Wed, 15 Nov 2023 22:27:00 +0000

Resolved - Google has resolved this issue. Everything should be back to normal. Please reach out to support@bowlr.app if that is not the case for you. (02:44 UTC — Nov 16)

Investigating - Many Bowlr users are experiencing issues ranging from not being able to sign in to the app reporting purchases incorrectly. The root cause of this issues is an underlying issue with the Google database service Bowlr uses. Unfortunately, there is no workaround at this time. Google support engineers are working to resolve the issue. (02:25 UTC — Nov 16)

[Resolved] iOS App (6.7.3) Crashes

Thu, 07 Jul 2022 11:32:00 +0000

Resolved - A temporary work around has been rolled out in version 6.7.4 that should resolve these crashes. (21:49 UTC — Jul 20)

Investigating - Version 6.7.3 of the iOS Bowlr app is being impacted by a bug in an underlying dependency that is causing the app to crash. Work is being done to help the underlying dependency resolve their issue. As a work-around, users can uninstall and reinstall the Bowlr app. You will not lose any of your data by doing this. (11:32 UTC — Jul 7)

[Resolved] iOS In App Purchase Issue

Wed, 28 Aug 2019 05:00:00 +0000

Resolved - Apple has finally approved the changes to the app that enable the Bowlr Pro upgrade to be purchased. Please ensure you are using version 3.1.6 to get this fix. This issue is now resolved. (14:00 UTC — Sep 6)

Update - Another build was submitted to the Apple App Store reviewers that hopefully will meet their criteria. (13:00 UTC — Aug 31)

Update - The Apple App Store reviewers are not allowing the fixed version to be published. We are working with them to get this published ASAP. (12:00 UTC — Aug 30)

Update - A fix has been submitted to the Apple App Store that will resolve this. (06:00 UTC — Aug 28)

Investigating - The in app purchase to upgrade to Bowlr Pro is not working on iOS. This will not impact usage of the app if you have 12 games or fewer. It will impact usage if you try to add a 13th game. (05:00 UTC — Aug 28)

[Resolved] Error When Entering In Frame-By-Frame Scores

Sat, 13 Oct 2018 17:30:00 +0000

Resolved (iOS) - The issue has been identified and resolved in iOS. (14:09 UTC — Oct 15)

Resolved (Android) - The issue has been identified and resolved in Android. (18:00 UTC — Oct 13)

Investigating - Some users are reporting getting the error NoSuchMethodError: The getter ‘alwaysShowFrameScores’ was called on null.. A bug has been identified that presents the above mentioned error when a user tries to enter in scores in frame-by-frame mode. To work around this error, users can open up the app settings and toggle the “Always show frame scores” switch from off to on and the back to off. (17:30 UTC — Oct 13)