<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <link rel="alternate" type="text/html" href="https://status.bowlr.app"/>
    <title>Android App on Bowlr Status</title>
    <link>https://status.bowlr.app/affected/android-app/</link>
    <description>Incident history</description>
    <generator>github.com/cstate</generator>
    <language>en</language>
    
    <lastBuildDate>2023-11-15T22:27:00+00:00</lastBuildDate>
    <updated>2023-11-15T22:27:00+00:00</updated>
    
    
    
      <atom:link href="https://status.bowlr.app/affected/android-app/index.xml" rel="self" type="application/rss+xml" />
    
    
      <item>
        <title>[Resolved] Google database failures</title>
        <link>https://status.bowlr.app/issues/2023-11-15-google-service-interruption/</link>
        <pubDate>Wed, 15 Nov 2023 22:27:00 +0000</pubDate>
        <guid>https://status.bowlr.app/issues/2023-11-15-google-service-interruption/</guid>
        <category>2023-11-16 02:44:00</category>
        <description>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.</description>
        <content type="html">&lt;p&gt;&lt;em&gt;Resolved&lt;/em&gt; - Google has resolved this issue. Everything should be back to normal. Please reach out to &lt;a href=&#34;mailto:support@bowlr.app&#34;&gt;support@bowlr.app&lt;/a&gt; if that is not the case for you. 
  &lt;span class=&#34;faded&#34;&gt;(02:44 UTC — Nov 16)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - 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. 
  &lt;span class=&#34;faded&#34;&gt;(02:25 UTC — Nov 16)&lt;/span&gt;

&lt;/p&gt;
</content>
      </item>
    
      <item>
        <title>[Resolved] Error When Entering In Frame-By-Frame Scores</title>
        <link>https://status.bowlr.app/issues/2018-10-13-error-frame-by-frame/</link>
        <pubDate>Sat, 13 Oct 2018 17:30:00 +0000</pubDate>
        <guid>https://status.bowlr.app/issues/2018-10-13-error-frame-by-frame/</guid>
        <category>2018-10-15 14:09:00</category>
        <description>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 &amp;lsquo;alwaysShowFrameScores&amp;rsquo; 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.</description>
        <content type="html">&lt;p&gt;&lt;em&gt;Resolved (iOS)&lt;/em&gt; - The issue has been identified and resolved in iOS. 
  &lt;span class=&#34;faded&#34;&gt;(14:09 UTC — Oct 15)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Resolved (Android)&lt;/em&gt; - The issue has been identified and resolved in Android. 
  &lt;span class=&#34;faded&#34;&gt;(18:00 UTC — Oct 13)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - Some users are reporting getting the error &lt;strong&gt;NoSuchMethodError: The getter &amp;lsquo;alwaysShowFrameScores&amp;rsquo; was called on null.&lt;/strong&gt;. 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 &amp;ldquo;Always show frame scores&amp;rdquo; switch from off to on and the back to off. 
  &lt;span class=&#34;faded&#34;&gt;(17:30 UTC — Oct 13)&lt;/span&gt;

&lt;/p&gt;
</content>
      </item>
    
  </channel>
</rss>
