redwood: Context does not always expose the currentUser

I’m using several services that rely on authentified user and I noticed a buggy behaviour.

This would be my sample code:

export const createStructure = async ({ input }: CreateStructureArgs) => {
  const { accountId, ...user } = context?.currentUser

  // irrelevant code goes here
}

It is tested using this:

scenario('Creates a Sale Enabled Team', async (scenario) => {
    mockCurrentUser(scenario.user.one)

    const result = await createStructure({
      input: Seed.Structure(),
    })

  // irrelevant expectations shamefully hidden here

  })

Now here’s what’s blocking me:

• my tests on that service rarely fail
• they mostly fail when tests are run only on the filtered file
• they almost never fail when all tests are ran
• my front application will always crash on that code, locally and online.

Output of the error:

api | TypeError: Cannot destructure property 'accountId' of '_b' as it is undefined.
api | 
api | at /Workspace/sport-office/api/dist/services/structures/structures.js(Object.createStructure):236
api | 231    input
api | 232  }) => {
api | 233    var _a;
api | 234    import_logger.logger.debug(import_api.context);
api | 235    const _b = (_a = import_api.context) == null ? void 0 : _a.currentUser, {
api | 236      accountId
api | 237    } = _b, user = __objRest(_b, [
api | 238      "accountId"
api | 239    ]);

Introduced a couple of weeks ago but I thought it was some random issue, now it’s more pressing.

RedwoodJS v0.36.4 Auth provider: Firebase