Right now calling realm.subscriptions.update inside an initialSubscriptions update callback results in a cryptic error, because the code is already running inside a subscription update transaction. Users should use the first subs argument passed to the update callback instead to directly mutate the subscription set.

This is documented but it could be confusing, so it may be worth throwing a clearer error if we can detect that a user is doing this.