The user object has a data property on its profile which contains the metadata fields we have defined in the custom JWT authentication settings.
This data property can only be accessed if we ignore the StitchUser type of the user object and treat it as any instead.
Looking at the source it seems there is a difference between the user object at runtime. The profile property is specified as readonly profile: StitchUserProfile but when debugging it is of the type ApiCoreUserProfile.
The user object has a
dataproperty on itsprofilewhich contains the metadata fields we have defined in the custom JWT authentication settings. Thisdataproperty can only be accessed if we ignore theStitchUsertype of the user object and treat it asanyinstead. Looking at the source it seems there is a difference between the user object at runtime. Theprofileproperty is specified asreadonly profile: StitchUserProfilebut when debugging it is of the typeApiCoreUserProfile.