Hey thank you for the feedback. I took a look into the code and don't yet see where this delays something. On the one hand it looks very similar to await client.onSync.stream.where(//Filter here for desired account data key and actually it was like this before but has been changed (don't know the reason maybe filtering in sync had problems with type escaping?)

However the current approach is just to wait until the next sync is finished and then check again what we have in memory and repeat this. While this is only waiting for the next sync if account data is not updated. This does not delay anything as we have to wait for the sync anyway to continue. I don't see where this would be faster than filtering the sync stream

Yeah, I get what you mean. I don't have an easy proposal on how to better handle this. But fact is, on a completely new account, this causes SSSS bootstrap to take 5 - 10 minutes since each and every account data change first runs into a network timeout of 40 seconds (default SDK behavior) since there is nothing to sync. One approach might be to add fake syncs to the stream similar to sending an event in a room in order to have the updated account data available immediately after it was uploaded.

@TheOneWithTheBraid I tried now several things. I took a look into the code where we use Client.oneShotSync(). A good example is probably this one in the ssss.dart:

    await client.setAccountData(
      client.userID!,
      accountDataTypeKeyId,
      content.toJson(),
    );

    while (!client.accountData.containsKey(accountDataTypeKeyId)) {
      Logs().v('Waiting accountData to have $accountDataTypeKeyId');
      await client.oneShotSync();
    }

I absolutely see no way how this could timeout. If the sync comes down so fast even before the client.setAccountData returns, the client.accountData.containsKey(accountDataTypeKeyId) check would still be false. As this is a while and not a do-while loop, we are not running into the await client.oneShotSync();. It is similar for all other places where we use this.

Also I tried to create a complete new account and did a first bootstrap. I wasn't able to reproduce the problem. Can you maybe provide clear steps to reproduce or a minimal coding example?

You could also check if you see something in the logs. Every time we call client.oneShotSync() a log is added. Make sure that you set loglevel to verbose please. This could give you a prove that the waiting time really comes from the oneShotSync.