josephatkuvio
commented
3 years ago @psandgren this appears to be a duplicate of #2102. I'm seeing the same error for multiple types of new activities on Android.
Closed psandgren closed 2 years ago
josephatkuvio
commented
3 years ago @psandgren this appears to be a duplicate of #2102. I'm seeing the same error for multiple types of new activities on Android.
psandgren
commented
3 years ago Good observation! Hopefully that will point the devs in the right direction.
PaulSorauer-IPG
commented
3 years ago +1 from me
I've encountered this with the MSAL client acquiring a token. It appears to be a breaking change with Preview 7.
I had this working fine in Preview 6:
authResult = await App.PublicClientApp.AcquireTokenInteractive(scopes)
#if __ANDROID__
// Xamarin Android-specific code
.WithParentActivityOrWindow(CrossCurrentActivity.Current.Activity)
#endif
.WithUseEmbeddedWebView(true)
.WithAccount(firstAccount)
.WithPrompt(Prompt.SelectAccount)
.ExecuteAsync();where 'CrossCurrentActivity.Current.Activity' was set in Platforms/Android/MainApplication.cs:
public override void OnCreate()
{
// Use the CrossCurrentActivity pluggin to assist in activity management within Android
CrossCurrentActivity.Current.Init(this);
base.OnCreate();
}Just to be thorough, I tried to downgrade Microsoft.Identity.Client to the same version that is meant to be working in the Maui WinUI project - 4.16.1 - but this version presents the same issue still.
Makes sense of what #2102 is saying, RE Android's ability to launch a new activity - I'm seeing the exception occur when my app attempts to open in the embedded browser but the screen remains black and then the exception is thrown.
Cheers,
Paul
mattleibow
commented
3 years ago Having a look at that stack trace I think we fixed that shortly after releasing P7. Previously we assumed there was always Window since you started from one. But in some cases, this was not true.
It should be fixed in RC1. You can test out the current CI builds using this Wiki: https://github.com/dotnet/maui/wiki/Installing-.NET-6
PaulSorauer-IPG
commented
3 years ago Having a look at that stack trace I think we fixed that shortly after releasing P7. Previously we assumed there was always Window since you started from one. But in some cases, this was not true.
It should be fixed in RC1. You can test out the current CI builds using this Wiki: https://github.com/dotnet/maui/wiki/Installing-.NET-6
Hi @mattleibow
Thanks so much for following up on this. Very helpful to get the CI build of RC1.
Just because I had some sources of confusion initially, and to help other peeps get through this more quickly, I have a couple of notes on how I worked through this:
maui-checkdotnet workload install, e.g. dotnet workload install android-aot --source https://aka.ms/dotnet/maui/main/index.json etc
Hope that helps someone work through the manual process of getting the RC1 CI build installed.
PaulSorauer-IPG
commented
3 years ago Having a look at that stack trace I think we fixed that shortly after releasing P7. Previously we assumed there was always Window since you started from one. But in some cases, this was not true.
It should be fixed in RC1. You can test out the current CI builds using this Wiki: https://github.com/dotnet/maui/wiki/Installing-.NET-6
Hey @mattleibow
There appears to be no maui-blazor workload published yet...
Any ideas when the blazor version will be available at that source? I'm loathe to install the Preview 7 maui-blazor over the top of RC1. It wouldn't work, would it?
Cheers.
mattleibow
commented
3 years ago The maui-blazor is not a workload, it is just a template. Not sure what you mean maybe...
PaulSorauer-IPG
commented
3 years ago The maui-blazor is not a workload, it is just a template. Not sure what you mean maybe...
Oh dear. 🥺 Withdrawn. I got confused with dotnet new maui-blazor 🤦♂️ Too much work and too little sleep last night.
Thanks for the response @mattleibow
PaulSorauer-IPG
commented
3 years ago Having a look at that stack trace I think we fixed that shortly after releasing P7. Previously we assumed there was always Window since you started from one. But in some cases, this was not true.
It should be fixed in RC1. You can test out the current CI builds using this Wiki: https://github.com/dotnet/maui/wiki/Installing-.NET-6
Hi @mattleibow
Can you confirm that the https://aka.ms/dotnet/maui/main/index.json 'source' listed on that wiki page is the correct ongoing NuGet feed to use for the RC1 CI build? I think this is meant just for MAUI?
I have it resolving to https://pkgs.dev.azure.com/xamarin/public/_packaging/maui-main/nuget/v3/index.json but this NuGet feed doesn't list the packages that are referenced in the Blazor WebAssembly 6.0 RC1 project templates that just installed:
I did try to manufacture a feed based on the name of the dotnet SDK installer, https://pkgs.dev.azure.com/dnceng/public/_packaging/6.0.100-rc.1.21424.1-shipping-1/nuget/v3/index.json but of course that was just a guess and it didn't work. 😁
Could you supply feed aligned to the RC1 CI build, please?
Cheers mate.
PS: Might be a good idea to pop it into the wiki page too. 👍
PaulSorauer-IPG
commented
3 years ago Having a look at that stack trace I think we fixed that shortly after releasing P7. Previously we assumed there was always Window since you started from one. But in some cases, this was not true.
It should be fixed in RC1. You can test out the current CI builds using this Wiki: https://github.com/dotnet/maui/wiki/Installing-.NET-6
For anyone that's interested, the wiki that @mattleibow references above has been updated and now includes an example of a custom nuget.config file with an pre-release RC1 nuget feed in it.
mattleibow
commented
2 years ago It has been some time and sorry for not checking in earlier. Is this still an issue?
From your last comment it appears that you managed to get things working? And, since we published preview 10 just days ago, hopefully all is resolved and apps re shipping 😄
I am closing this for now as I got happy vibes, but if that is just because you are just awesome for trying maui and you are still having issues, please re-open with any additional info that has changed.
josephatkuvio
commented
2 years ago I can confirm that .NET 6 RTM seems to have resolved this issue for the MSAL/B2C side of things. I've seen other references for a similar issue with FilePickers but haven't tracked that one.
Description
Trying to get AAD B2C working, porting the ADB2CAuthorization-example, and getting a hard crash with System.InvalidOperationException: 'Window Not Found' in the debug log. Is there any good example of how this should be done? Hopefully I'm doing it wrong :)
Steps to Reproduce
Setting up the client in App.xaml.cs:
Calling to get token:
Expected Behavior
Opening a browser tab to login
Actual Behavior
Hard crash with the message "Window not found". I can see
Basic Information
Logs