When I turn on the tablet mode or the phone mode in Chrome, I get a javascript error :
Uncaught TypeError: Failed to execute 'elementFromPoint' on 'Document': The provided double value is non-finite.
at HTMLHtmlElement.avp.disableTouchSafari (viewer3D.min.js:18)
I've just update Chrome to the last version.
Any idea?
This might an issue of Forge Viewer. Apologizing for any inconvenience caused.
I have logged a request LMV-3401 [Autodesk.Viewing.Private.disableTouchSafari() reports error while viewing model with Chrome DevTools' Device Mode in macOS] to our development team to allocate time to investigate. As it requires further exploration and possibly a modification to our Viewer, please make a note of this number for future reference.
You are welcome to request an update on the status of this request or to provide additional information on it at any time quoting this request number via forge.help#autodesk.com.
However, I think this error didn't affect main features of Viewer. At the meanwhile, I think a real mobile device will help you in this case since this error didn't show up while testing on my Ipad.
Cheers,
Related
While loading a product into the Forge viewer using latest version of Chrome, user receives a message that states "WebGL context lost". They had a model loaded into the viewer which was working fine, clicked on another model to view it and that is when they received the error message (see attachment).
Is there anything that can be done to mitigate or resolve this issue?
Click for Picture of Error Message
Here are two possibilities for this issue:
The graphic card driver is out-date, please try to upgrade it: https://knowledge.autodesk.com/support/bim-360/troubleshooting/caas/sfdcarticles/sfdcarticles/Error-WebGL-context-lost-when-viewing-files-in-BIM-360.html
There might be some viewer instances that haven't been destroyed properly. you can type NOP_VIEWERS in your browser console to see if the array length is greater than two. To fix this, you can take advantage of viewer.finish() before loading other models.
I was following this guide on native messaging, but now I've come to a stand-still. The developer console on Firefox keeps giving me the same error:
"Attempt to postMessage on disconnected port" along with "Webconsole context has changed" before it.
I've checked the registries, the ping_pong registry key is in the correct place,
HKEY_LOCAL_MACHINE\\SOFTWARE\\Mozilla\\NativeMessagingHosts\\ping_pong,
and it's value is pointing to the location of my manifest.json file.
My extension id and "allowed_extensions" match.
I found this, and it did stop at the end saying I don't have a python script in the batch file, but that shouldn't be the cause of my error messages.
I have Firefox Quantum 61.0.2, if that's of any use.
What am I doing wrong?
This is a generic error and it means the native messaging host configuration is wrong. The specific error is logged in the Browser Console (Firefox Menu --> Web Developer --> Browser Console) and it is much more helpful.
(For me, the specific error was a typo in the native messaging manifest.)
(Discussed in: https://github.com/mdn/webextensions-examples/issues/266)
How to go about this error "Launch terminated : ERROR: Course launch was canceled because the HACP getParam failed to find the user information". cannot open the web page beacause of this.
The reason for this is that you might have left the browser idle for a long time and the session got logged out.
Solution: Login to the Skillport or other Portal which is linked to the Skillport, and everything should be all set.
Please be more specific. Which website? Which browser?
Googling the error (which you should have done first) yields this result:
I get the Skillsoft error: “Launch terminated: ERROR: Course launch was cancelled because the HACP getParam failed to find the user information”:
Per our Required Browser Settings document, please ensure that *.skillport.com is added to your Trusted Sites zone in Internet Explorer.
If you're not on "skillport.com", whatever it is, you'll probably want to add the domain you're on to the Trusted Sites instead.
My UWP apps suddenly throw the following exception on Win 10 Mobile Build 10.0.14342.1001. They still work fine in the emulators.
Is anybody experiencing the same problem? Is there a workaround?
Exception thrown: 'System.ArgumentException' in mscorlib.ni.dll
WinRT information: user
Additional information: The parameter is incorrect.
user
To ensure the problem is not related to something specific with the apps email messages I sent the following simple message which causes the same problem.
Dim em As New Windows.ApplicationModel.Email.EmailMessage
em.To.Add(New EmailRecipient("a#b.c"))
em.Subject = "test"
Await EmailManager.ShowComposeNewEmailAsync(em)
Link to test case.
This is a bug in the insider build. No workaround known.
MS was informed about it via feedback and the MS forum.
Got fixed with Windows 10 Mobile Insider Preview Build 14356.
Build 14342 is an insider 'fast' build, meaning it is not production-ready and you are likely to hit errors from time to time. Please file feedback using the Feedback Hub, and wait for the next build. Thanks for being an Insider!
I have a Windows Phone 8.1 app with Google login, which uses the
GoogleWebAuthorizationBroker.AuthorizeAsync
method. 90 % of the time, the authentication works, however, occasionally, the app just crashes on this line (I am logging right before it, so I am sure). I have the call wrapped inside try - catch, but that doesn't seem to work - exception is never caught.
I am also sure I am calling the method on a UI thread, I am using the DispatcherHelper from MVVMLight for that.
The fact that I am not able to reproduce the crash complicates this a lot, I have not experienced it with debugger attached, only in Release mode, on target device, run locally.
Do you guys have any ideas / clues / pointers? I know I'm not providing a lot of information, but I don't have any..
EDIT> So the error now happened with debugger attached - and the app just froze, last message in Ouput window was
"WinRT information: Cannot get credential from Vault"
But that's normal behavior..