Scouting Mobile App Logs you out and requires a force quit to login

Parents, myself included, are reporting that the red Scouting mobile app logs out parents and requires a force quit of the app to be able to login again.

We’re trying to migrate to this app for the new RSVP system. We need this app working rock-solid to make an easy transition. I usually try to have some more information, but I don’t have a lot for this one… Any help would be great as we roll out our new Pack comms strategy Sept 1.

@RyanHendrickson

We will report this but frankly logging in directly to https://advancements.scouting.org (Scoutbook Plus) is more reliable than using the Scouting App.

Thanks… Anecdotally from our Pack, Parents want user friendly mobile apps, like TeamSnap, to RSVP their kids from anywhere - lots of times in the car. They don’t want to pull out a laptop to have to login and do it.

Here’s the app this morning after having logged in yesterday:

I tried to log into it and received this error:

I then had to force quit the app and login. Everything worked fine after this. We’re really trying to lean into this app this year, so the initial experience of logging in needs to be great for parents.

Thanks for checking into this/reporting it up,
Let me know if there’s anything else I can provide to help figure it out,
Ryan

One thing to be aware of (if you haven’t already seen it elsewhere) is that the app was not updated for the new cub scout program, so at the moment it’s largely dysfunctional for packs (putting aside the general functionality issues you raised here).

On the TeamSnap front, keep in mind that app is largely available “free” via a combination of being adware and using the paid tiers to fund the development of the “free” tier. I’m not maligning the business model, just pointing out that it’s a very different structure. If the BSA charged units for Scoutbook/SB+ and the app what TeamSnap charges for their system (and required individuals to either pay or put up with adware), units and families would be up in arms. We already regularly hear complaints about various fees. Again, not maligning TeamSnap in particular or adware in general, but it’s important to understand the differences between the BSA’s model and that of more commercial entities.

I did see that someplace, but I thought I also read it’s scheduled for an update for the new year. Is that accurate?

The website has been charging with updates all summer, that’s awesome! The mobile app feels decent. The primary use case we have is allowing parents to easily RSVP their scouts for events via it.
#1 Reliably login and/or stay logged in.
#2 RSVP for event.

I’d love to see future features too, like communications within the Pack, but those are the two primary goals going into the new season.

Good question. I don’t know, and I’m not sure the SUAC folks could say either way. I assume the intent is to “catch up” with the new program, but I don’t know either way. I agree that, at least, it shouldn’t require a force quit to be used.

@RyanHendrickson

You don’t need a laptop to rsvp his https://advancements.scouting.org. It works fine on a mobile device.

@RyanHendrickson just out of curiosity, which type of login do you use for Scoutbook? Username/password, AppleID, GoogleID?

There was previously an issue in the app with AppleID causing this sign in error and having to force quit the app to be able to sign in. It was fixed previously (and still appears to be fixed). Would be curious to report if one of the other two types of logins is now doing the same thing. We’d need more info on the OS version of the device and app version you are running to report to developers for further debug.

As for staying logged in, I doubt that will happen. Other posts have explained BSA’s stance on protecting PII and thus enforcing a strict timeout and need to log back in to each app or web page.

I am running Android 14 (AP2A.240705.005) and logging in with Google SSO. The app version is: version 2.6.0
com.bsa.sbm

I understand the privacy concerns, but that can be alleviated using device-level logins like pin, fingerprint, pattern, etc. to make it secure and convenient to use. You can force a reauthentication once every 30 days.

Thanks,
Ryan

@RyanHendrickson the developers were unable to replicate this issue in their test environment. Is there a chance you can capture a screenshot video of this occurring so they can see to further debug?

Yes I can, just did it, is there a way to privately send that screen recording?

@RyanHendrickson I will start a private message with some of the other SUAC copied to send it to us. The message request will show up in your notifications in the top right.

Replying back now in the pm with the video…

Just pinging for an update and to keep this open.

@RyanHendrickson

Keeping the thread open will not get the issue fixed any faster. When there is a fix a new version of the app will be released and it the fix should be noted in the app release notes.

The only update we can provide is to say the developers are aware of the issue. We do not know when it will be addressed and cannot comment when it is being worked on.

2 Likes

I didn’t know this. This is very good to know.

Here is an example for all:

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.