Administration -> "Edit Extended Information" error when trying to "Invite a Scout to Connect"

Scoutbook Scoutbook Bugs
1

Screenshot 2024-07-21 at 11.51.59
Screenshot 2024-07-21 at 11.51.592594×1432 352 KB

I am getting this persistent error when trying to invite my child to connect. My child has recently bridged to a Troop after Lion->AOL in a cub scout pack. My understanding is that this “Invite a Scout to Connect” capability in the “Edit Extended Information” section (of my scoutbook dashboard, administration section) is the correct way to invite my child to create their own account in scoutbook. From reading the forums and help here, I believe that if my child already had an account, there would be a “delete account” option on this same page. This is also the documented method that our troop has been using for years to accomplish a scout’s account creation.

I have been attempting and reattempting this operation for several days. I have tried logging out/back in, using chrome incognito mode, using a different browser, etc, etc. Nothing resolves the error. Looking in the developer tools, it is definitely coming from scoutbook, in the response object of the invitation call.

The SB/BSA ID’s involved are:
Parent’s IDs: (SB: 2747072, BSA: 12950022)
Child’s IDs: (SB: 2753516, BSA: 135978133)

Please help.

2

I also tried my child’s personal gmail account, as their troop email is a tad long. Same result.

3

@WilliamPressly first guess is “-” in last name - try these instructions - once you have that the same credentials can be used for Scoutbook

Myst Account Setup.pdf (223.2 KB)

4

And use a unique email to avoid duplicate email warnings

5

Thanks! those instructions worked.

So, just for clarity, there is something in the code path around the “edit extended information”->“invite to connect” that is choking on the dash in the email, or the dash in the last name? Just curious so we can update our troop’s documentation. I assume it is the email?

6

I do not follow the point here about unique email warnings. I have not seen any such warning nor am I using duplicated emails?

7

It was more in the way of advanced warning to avoid an (apparent,) error message. The system permits non-unique emails, but throws a warning message when they’re encountered.

8

fwiw, I kinda guessed that some email validation might be choking on the dash in the email, and I tested a gmail address that had no dash to the same result. maybe the code there is just broken?

9

ah, yes. sorry all. rereading, that is definitely what Donovan was warning about. I misread that.

1 Like
10

@WilliamPressly The dash in the last name.

1 Like
11

Hi Jennifer — thanks for the clarity there. Is this a known issue? Was it confirmed in the code/error logs? Just curious how I should update our troop’s documentation on this issue.

If it is a code bug, that we have no eta on a fix, I can just append the pdf of directions that Donovan provided earlier in the thread with a qualification like “if you are seeing issues with the “edit extended information”->”invite scout to connect” email invitation (dashes in scout’s name have been seen to be a problem) then consult this documentation to create a new account, by matching on your scout’s existing profile”. And then reference Donovan’s pdf.

Or something like that.

Thanks for all of your help! This was a quick resolution — I just wanna update our docs accordingly for those that follow.

1 Like
12

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