{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
впервые опубликовано в:BungieNetPlatform
Смотреть всю тему
1/22/2017 3:37:11 AM
2
Android OAuth Trouble
Hi everyone,
I'm trying to use the new OAuth2 support for an Android app. I'm running into issues with the redirect URL field.
I've read the help article here: https://www.bungie.net/7_Developers-Bungienet-Authentication/en/Help/Article/45481, which says, ". If you are creating a mobile app, the Redirect URL may use a scheme that uniquely identifies your application which will be launched by the platform." However, I haven't been able to save a redirect url that doesn't start with https
I haven't ever written anything using OAuth before, so it's possible I'm missing something. Any help would be appreciated!
-
Изменено (Callisto): 8/25/2017 4:31:05 PMThis is due to Bungie.net using an incorrect URI validation regex for AnyUrl: [quote] }, n.validateAnyUrl = function(n) { var i = n.val(), r = !1, u; return i.length > 0 && (u = /^[a-z\-]+:\/?\/?([\w\-_\.]+)+([\w\-\.\(\)\!,@?^=%&:\/~\+#]*[\w\-\@?^\!=%&\/~\+#])?$/i, r = !u.test(i)), this.createValidationResult(r, n, t.anyurl) [/quote] As noted at https://github.com/Bungie-net/api/issues/5 Bungie, please alter ^[a-z\-]+: to ^[a-z\-.+]+: in the regex above. App authors, avoid using "." in your callback URI scheme if you need an urgent workaround.
