chrome canary ARC apps not running - google-chrome-arc

I have installed chrome canary and added the ARC Welder. I see an warning of not running ARC welder on chrome OS. When I add an APK to test I see an error "uncaught TypeError:chrome.runtime.getManifest is not an function ". How do I solve this error?
UPDATE:i don't see this error anymore the only errors i see now are "plugin not ready" and "plugin crashed:captured minidump".

This could be because you are using also the Canary version of the ARC Welder and ARC Runtime environment. Because it's a canary version there will be bugs in it. Chances are that the next day the error will be gone.

Related

Unable to find module for DevMenu - after upgrading to Expo 44

I'm going crazy - when I launch the app on a real device, I'm getting Unable to find module for DevMenu and the whole app is frozen on the splashscreen. I have seen this which alludes that if I turn off remote debugging, it could fix it, but the app is completely unresponsive, so when I shake it, the Expo options don't show up.
When I launch it on a simulator, I see the error, but it's not fatal. Again, I can not seem to open the Expo menu anymore on the simulator to test if it is the remote debugger causing the issue. But the app runs fine on the simulator, other than that.
What is the error Unable to find module for DevMenu and how can I fix it?
Real device:
Simulator logs:
I had the same problem. What solved it was to install expo-dev-menu :
npm i expo-dev-menu
And importing it in my App.js.
import 'expo-dev-menu';
Hope it helps!

Nativescript 7 and Chrome DevTools

I have updated my app to Nativescript 7. One thing I haven't been able to get to work correctly is debugging using Chrome Dev Tools. It does use the Chrome Dev Tools console, but I can't seem to get the Network tab to work or the Elements tab. Has anyone else managed to get it to work?
My app uses Angular 10 and Nativescript 7.
I believe they fixed this in a recent update for NS. Try updating and see if that fixes it.
If not you can update your package.json file to use "#nativescript/ios": "6.5.3",. That'll use the JSC compiler for iOS instead of the new V8 runtime, then your element and network inspector should work!

Latest Sidekick update causes VBoxManage failed exit code 126

Just installed the latest update Version 1.14.0-v.2018.11.15.3(latest). Install updated Nativescript CLI to 5.01, but on starting Sidekick I now get an error as per the title of this post followed by VirtualBox.app No such file or directory.
Thank you for bringing this issue to our attention.
The reason why you get this error when opening an app in Sidekick is because Sidekick tries to get the emulator images available on your machine at this point and fails. This is related to a feature we introduced recently - you can now start an emulator from Sidekick UI.
Having said that, we'll resolve the issue by moving the code that gets the emulator images to execute when you actually open the emulator images dialog - that way, you will not get a confusing error initially, but will still get the errors, if any, if you want to use the new feature and there is a problem.

Unable to install Android / ARC app from Chrome Web Store on Chrome OS

I have an Android app which I "made into" a Chrome OS app by using ARC Welder, and published in Chrome Web Store (per documentation here: https://developer.chrome.com/apps/getstarted_arc).
https://chrome.google.com/webstore/detail/aquamail/immkckhpjjkikagmhfnpjjcnaelegjel
( the app is called AquaMail )
Now, I don't own any Chrome OS devices, so Chrome Web Store just says "wrong OS" for me, but...
Someone with a Chrome OS device was unable to install the app with this message:
Unable to install "AquaMail" because it is not allowed by "App Runtime for Chrome (Beta)"
How can I find out what's wrong?
As first step, I guess I'd like to get a more detailed error message, how can the user do that? Is there anything equivalent to logcat?
Or maybe someone from Google / ARC team can try installing as a sanity check?
Unable to install "AquaMail" because it is not allowed by "App Runtime for Chrome (Beta)"
This is an error message indicating the user has an older version of ARC than the current one available. There used to be a whitelist that controlled what apps could be uploaded and installed but it has since been removed. This error message is a whitelist restriction being enforced.
Have the user check what version of ARC they have in chrome://extensions with developer mode enabled, and compare to the version that is currently shipping via https://arc-omahaproxy.appspot.com
If it is not current, they can try clicking "Update extensions", or more drastically they could uninstall all ARC apps and reinstall.

locationManager didFailWithError null phonegap simulator

I am having following problem with the location service with IOS on the simulator:
using phonegap 2.2.0 with xcode 4.5.2,
Cordova.plist EnableLocation = YES
navigator.geolocation.getCurrentPosition(myPositionSuccess, myPositionError, {maximumAge: 300000, timeout:10000, enableHighAccuracy : true});
myPositionSuccess is never called, with following error at navigator.geolocation
locationManager::didFailWithError (null)
I just tried it on the simulator. Any Idea?
Exit the simulator & run your app again. Worked for me.
I was having the same error with XCode Version 4.3.2 & cordova/phonegap 2.1.0
The simulator was unable to get my location even when I ran Google Maps in Safari. That led me to the conclusion that it was more than just my project that was at fault.
I am still unable to figure out exactly why restarting the simulator worked, but there is one possible reason.
I usually shut down my Mac without quitting most of my running apps & the "Reopen windows when logging back in" option checked. The simulator, however, is one of the apps i definitely quit. But the last time I shut down, I did not quit it. So, like I said, possible reason.
Hope this helps you.
Another thing may be to check the location setting in your simulator, I believe the default setting is none which means the geolocation will not find anything. If you are running your simulator, go to Debug > Location > City Run or some other choice and then try to use the geolocation function again it should work fine.
I know this is a bit old but I was looking for an answer on this when I remembered the location setting so I figured I would post here for future reference in case anyone needs it.

Resources