We have a Silverlight application that runs OOB (out of browser) so the user can install it. When it's running OOB we display a button that calls Application.Current.MainWindow.Close() so that the user can exit the application. This works perfectly fine on windows, but causes an error saying the application has quit unexpectedly on OS X. Anyone have any ideas why this might be? Thanks!
Found out the problem. This is apparently a "protected" action and must be done directly in response to a user action. It cannot be scheduled to happen later (we were playing an animation on the button click and then after a timer expired trying to close the window; we have to just close the window).
An exception was actually thrown on the windows version, it just never displayed any sort of message box.
Related
So, we have a .net 5.0 wpf application which on startup loads a window containing a cef browser. The browser then loads our login form. The application is running on win 10 64 bit machines exclusively. This has worked without a problem for the past 6 months. Yesterday i installed the application on one of our customers' laptops. The installation went down without a hitch, but after the cef browser loaded the login form I was unable to interact with the input fields. By that I mean that if I put my cursor above the text field my cursor changes shape, but upon clicking no cursor would appear inside the text field and anything I typed wouldn't appear in the text filed. Clicking the Login button didn't have the expected effect of telling me that I am missing username and password, instead it moved the trigger areas of all input elements downward while they were still being rendered at the same position as before.
This problem is exclusive to this one machine. All other machines running the application aren't experiencing and never have experienced anything like this so i'm not expecting it to be a bug within cefsharp.
My question is if anyone has had a similar issue or any idea how to workaround it.
CefSharp version being used is 94.4.110.
I read through the docs and it seems to suggest that we need to run msal login via an async dialog because for office on the web, the taskpane starting point is not the topmost window.
However, on the PC platformtype, I think the taskpane is toplevel.
Does that mean that on the PC platform, I should be able to run a redirect dialog without issues directly in the taskpane itself?
I'm trying to use msal-browser (msal 2.0) but I keep getting the taskpane popping up a whole new browser tab outside the outlook desktop app and it breaks the login process. I'm not sure I'm doing it right though.
Does anyone have an example of running a redirect login process inside the taskpane itself for the PC platformtype using msal 2.0?
I did get this to work Ok. The new msal-browser 2.0 works fine and is probably more predictable than the 1.x series.
On iOS 11, there seems to be something different in the app state when an app is backgrounded using the home button vs when it opens an external webview link and goes to safari.
On returning to my app, I am requiring the user to validate with touch ID. If the app is backgrounded using the home button and returns, the call to LAPolicy.deviceOwnerAuthenticationWithBiometrics shows a prompt and waits for the user interaction. However, the user goes to an external website through a link in the app, and returns to the app using the "Back to app" button that shows in the status bar, a call to LAPolicy.deviceOwnerAuthenticationWithBiometrics results in an error immediately without displaying the touch ID prompt.
I've checked that the application state in both cases when the call is made is that the app is active. It's being done on the main thread, and it's being made on applicationDidBecomeActive.
This is the error I see:
Error Domain=com.apple.LocalAuthentication Code=-1004 "User interaction is required." UserInfo={NSLocalizedDescription=User interaction is required.}`
Any insights into the behavior of LAPolicy.deviceOwnerAuthenticationWithBiometrics? The code used to call it is:
let context = LAContext()
context.localizedFallbackTitle = ""
print("--> internalAuthenticateBiometrics background \(UIApplication.shared.applicationState == UIApplicationState.background)")
context.evaluatePolicy(LAPolicy.deviceOwnerAuthenticationWithBiometrics, localizedReason:NSLocalizedString("Place your finger to sign in.",comment: "")) { [weak self] (success, error) in
print("--> internalAuthenticateBiometrics completion success \(success) error \(error)")
}
We discovered that this specific issue was happening on older versions of iOS 11. We were testing on devices that had iOS 11.0.3 and 11.1.2. I updated my OS to 11.4 and the issue went away.
As of right now, I can only assume that Apple fixed some app foregrounding and biometrics issues. FYI this issue didn't have anything to do with the views being backgrounded or covered, because we made sure everything was visible, appDidEnterForeground was called, viewDidAppear was happening, and we even added delays in triggering biometrics after several seconds.
We are having problem with a Silverlight 5 app and IE11.
Suddenly, it's no longer possible to copy-and-paste from a Silverlight application to the clipboard, after upgrading to IE11.
When the Silverlight dialog that asks you for the right to access the clip-board appears, then IE11 freezes. This behaviour has also been verified on IE11 och two different Win 8.1 computers.
We have also tried to add the site to trusted sites, and 'Allow programatic access to clipboard" to Enabled. But it dosnt help.
Any suggestions?
Anyone knowing if this is something Microsoft is addressing?
/Erik
Ran into the same issue, running IE as administrator ended up clearing up the freezing issue.
From there you can then check the box to [remember my answer], click [yes] to allow clipboard access for this site, then restart IE (non-admin) and it won't freeze when accessing the clipboard.
I am developing an app for Windows Universal 8.1, facing an issue where the App gets Exit on going background. The scenarios are as follows
When the app goes background on clicking Windows key(FAS), the app get exit.
When I launch Share Task i.e Data Transfer Manager Interface, after completing the share operation the app exit.
Works fine in Debug mode but issue found after deploying to the device.
PS : I am using the Navigation Service Interface to navigate to pages using MVVM and navigating from viewmodels.
Please help if its known issue, if not help to rectify this.
Thanks in advance.
Sounds like your App crashes in The Suspending Event. As apps in Debug mode are not suspended, you are unlikely to see that happen.
You can manually fire the event from Visual Studio when debugging: It is in the debugging toolbar under Application Lifecycle Events.
Most common error in this case: Using complex objects as navigation parameters, which cannot be serialized.