You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I apologize before-hand if this is something that already exists, but I could not make this work, even when searching for this in the documentation.
We're trying to add a custom User-Agent header into the browser that opens the authorisation prompt. For this we tried to use both customHeaders and additionalHeaders for both iOS and Android, but we haven't been able to update the User Agent.
We've tried several combinations, like:
This resulted in a crash for iOS, with a 400 Bad Request being thrown.
additionalHeaders: {
'User Agent':
'Mozilla/5.0 (iPhone; CPU iPhone OS 17_5 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/17.5 Mobile/15E148 Safari/604.1 Test'
}
The following two had no impact whatsoever.
additionalHeaders: {
'User-Agent':
'Mozilla/5.0 (iPhone; CPU iPhone OS 17_5 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/17.5 Mobile/15E148 Safari/604.1 Test'
}
additionalHeaders: {
'UserAgent':
'Mozilla/5.0 (iPhone; CPU iPhone OS 17_5 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/17.5 Mobile/15E148 Safari/604.1 Test'
}
Is there any possibility for this feature to be implemented, or is it already present / can be done through a workaround?
Thank you for the support!
The text was updated successfully, but these errors were encountered:
I apologize before-hand if this is something that already exists, but I could not make this work, even when searching for this in the documentation.
We're trying to add a custom
User-Agent
header into the browser that opens the authorisation prompt. For this we tried to use bothcustomHeaders
andadditionalHeaders
for both iOS and Android, but we haven't been able to update theUser Agent
.We've tried several combinations, like:
This resulted in a crash for iOS, with a 400 Bad Request being thrown.
The following two had no impact whatsoever.
Is there any possibility for this feature to be implemented, or is it already present / can be done through a workaround?
Thank you for the support!
The text was updated successfully, but these errors were encountered: