In our last post, we looked at what we needed to do to setup our shared/portable project to authenticate with Autodesk Forge. Almost all of the code the important code is in the shared area, but we do have to do somethings within each of the platform projects. Lets check out UWP.
The first thing that I do is go into the Package.appxmanifest in the UWP project. Once you are in it, click on the “Declarations” tab. On this tab, you can declare lots of different things for your app: able to pick files, camera settings, background tasks among others. The one we are interested in is protocol.
Select protocol and add it to the list of the supported declarations. Give the protocol a name check “ExecutableOrStartPageIsRequired”. For the name, make sure that you give it something unique. Perhaps an abbreviation of your company followed by some kind of app designation.
Override UWP Application.OnActivated
In the UWP platform project, you need to override the Application.OnActivated function to handle the deep-link. Normally Xamarin Forms will just route the URI request to OnAppLinkRequestReceived, but it doesn’t seem to be working for UWP (or iOS). So what we will do, is just call in to a new entry point which then delegates to the protected function.
/// UWP application object
sealed partial class App : Application
// ... other stuff here
protected override async void OnActivated(IActivatedEventArgs args)
if (args.Kind == ActivationKind.Protocol)
var protocolArgs = args as ProtocolActivatedEventArgs;
DeepLink.App thisApp =
Then we can go back to the application object in our portable library and fix up the OnAppLinkRequestReceived function and the manual entry point we show above that is used for UWP and iOS.
public partial class App : PrismApplication
/// the rest of the class is up here ...
protected override async void OnAppLinkRequestReceived(Uri uri)
bool retrievedToken = await GetAccessTokenAsync(uri.ToString());
public void UwpIOSOnAppLinkRequestReceived(Uri uri)
All that is happening above is that when the app is activated because of the protocol that it has registered, it will look at the URL and extract the response code that was returned by Forge. It will then use that response code in a REST API call to get the authorization token and refresh token. If that is successful, we perform a navigation to the next page in our app. Obviously the code isn’t complete as it doesn’t handle any kinds of errors. For the details on how to get the authorization and refresh tokens see the previous post.
And that is it for UWP, just a little bit of code and we are back in our shared code base. Up next will be iOS.