Previously Google Maps works fine on my Android device. I did not change any code and certificates. Now I am getting the following error Log:
EDT] 0:20:38,90 - Exception: java.lang.RuntimeException - Waited too long for browser bridge
java.lang.RuntimeException: Waited too long for browser bridge
at com.codename1.g.d$a.a(MapContainer.java:262)
at com.codename1.g.d$a.b(MapContainer.java:223)
at com.codename1.g.d.a(MapContainer.java:709)
at com.zetta.survey.a.c.a(GoogleMapsTestApp.java:78)
at com.zetta.survey.d$2.a(MainMenu.java:144)
at com.codename1.s.r.a(Form.java:1621)
at com.codename1.s.ae$a$a.run(SideMenuBar.java:1745)
at com.codename1.s.n.l(Display.java:1101)
at com.codename1.s.n.j(Display.java:1045)
at com.codename1.s.n.i(Display.java:946)
at com.codename1.s.ad.run(RunnableWrapper.java:120)
at com.codename1.impl.b$1.run(CodenameOneThread.java:60)
at java.lang.Thread.run(Thread.java:818)
Any Suggestions?
For some reason the native maps are failing to initialize so it is falling back to the web-based maps - which shouldn't happen on device. Things to check:
Make sure your app has the android.playService.maps=true build hint.
Refresh cn1libs, and clean and build, then try again.
Try reading the device log in DDMS. There is surely an error reported when it fails to create that native map.
Related
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,
When trying to install a service worker (Chrome 55), I'm getting this error in the browser console.
Registration failed - could not retrieve the public key
But this is happening only in the browser in one of the devices. In other devices in chrome 55, it's working fine. I'm not able to replicate this issue in other devices with the same chrome version. So I suppose this is not a problem with worker or manifest files. I would be very happy somebody could throw some light on this issue.
I got some advice from service worker discuss group regarding this error. Peter who is part of Chromium project says that
"This is the sort of error that fits in the "this should never happen"
category. The only situation in which this would happen is when the
on-disk GCM Key Store database got corrupted and, for some reason,
cannot be recovered."
and Matt pointed me to this : https://cs.chromium.org/chromium/src/content/public/common/push_messaging_status.cc?type=cs&q=%22could+not+retrieve+the+public+key%22&sq=package:chromium&l=49
So this bug happens to be in "should never happen" category. Luckily when I restarted the machine, in which the chrome was throwing this error, the error disappeared and it started working fine.
Read more about this here : https://groups.google.com/a/chromium.org/forum/#!topic/service-worker-discuss/gCFxq4fHPVw
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..
I am creating an application that until yesterday seemed to work, but this morning, performing a function as I always do, it turns out this message:
"Fatal error: Uncaught OAuthException: An active access token must be used to query information about the current user. Thrown in ../base_facebook.php on line 1254"
Where am I doing wrong?
you Try to clean the cookies and cache from your firefox browser and try to execute your application once again...and check if you are app works in firefox this time...
I'm coming across this bug , while running my Polymer Element inside a mobile browser. Chrome in this case.
DOMException {message: "Failed to execute 'dispatchEvent' on 'EventTarget': The event provided is null.", name: "InvalidStateError", code: 11, stack: "Error: Failed to execute 'dispatchEvent' on 'Event…/packages/shadow_dom/shadow_dom.debug.js:2678:12)",
INDEX_SIZE_ERR: 1…}
"Error: Failed to execute 'dispatchEvent' on 'EventTarget': The event provided is null.
at o.Map.Tap.o.Handler.extend._simulateEvent (http://cdn.leafletjs.com/leaflet-0.7.2/leaflet.js:9:5230)
at o.Map.Tap.o.Handler.extend._onUp (http://cdn.leafletjs.com/leaflet-0.7.2/leaflet.js:9:4807)
at Document.t.(anonymous function).s (http://cdn.leafletjs.com/leaflet-0.7.2/leaflet.js:8:20285)
at invoke (http://localhost:8080/packages/shadow_dom/shadow_dom.debug.js:2805:28)
at dispatchBubbling (http://localhost:8080/packages/shadow_dom/shadow_dom.debug.js:2753:12)
at dispatchEvent (http://localhost:8080/packages/shadow_dom/shadow_dom.debug.js:2706:9)
at HTMLDocument.dispatchOriginalEvent (http://localhost:8080/packages/shadow_dom/shadow_dom.debug.js:2678:12)" shadow_dom.debug.js:2816
It only occurs in a mobile browser, when using Google Maps or Leaflet maps which involves using the
import 'dart:js';
library. There is a bug report which seems to be same issue here https://code.google.com/p/dart/issues/detail?id=16125, but no answer of how to deal with it.
To see if the same issue affected Leaflet I also implemented it using the
'dart:js'
library, but get the same issue.
Is there a solution/work around for this?