I added extension in app manifest
I added protocol name open
And launch from app2
by launcher
await Launcher.LaunchUriAsync(new Uri("open://useLess?GetPage2"), options);
App is launching but after few seconds it will close automatically
Related
I have published a native messaging add-on on Mozilla, but the native messaging host (native app) runs only once, if I restart firefox, the native app does not start.
Here is the scenario:
Step 1: I install the native app on Windows 10 using the setup file, the setup also configures the registry key under
HKEY_CURRENT_USER\Software\Mozilla\NativeMessagingHosts
HKEY_LOCAL_MACHINE\Software\Mozilla\NativeMessagingHosts\
Step 2: Start firefox, download and install the public released (signed) add-on from mozilla. The add-on icon shows on Firefox, I click the icon, the add-on popup page shows, click the menu items on the popup, the add-on works as expected, the native app works too, it receives messages from add-on, and sends messages back to the add-on.
All is OK, it seems the native messaging add-on works well. However, after I restart firefox, click the add-on icon, click the menu items on the popup menu, nothing happens. I type about:debugging, in the console window, there is error message "Unchecked lastError value: Error: port is null".
This error only happens while using the signed add-on, using local version un-signed addon, the native messaging host and add-on always run, no such problem.
I want to know, when download and install the addon from Mozilla, except the addon's XPI file, are there other files also downloaded? Maybe these other files run after firefox restarts, and these files or their configuration prevent the native app from running.
Here is the code snippet in background page:
function connectToNativeHost()
{
var nativeHostName = “com.some-company.test”;
port = chrome.runtime.connectNative(nativeHostName);
console.log(port)
port.onMessage.addListener(onNativeMessage);
port.onDisconnect.addListener(onDisconnected);
}
function onDisconnected()
{
console.log(chrome.runtime.lastError);
console.log(‘disconnected from native app.’);
port = null;
}
I test again and again, I find that after firefox restarts, the native app never runs again, firefox does not create a process for the native app.
Thank you for your help!
I have created basic sample application and integrated angular/pwa. In ngsw-config .json file i added datagroups for api call. Now i can able to download the application and api call is working fine in offline too.
After that i moved to my application and did the same for pwa. Now api call is not working in offline. I checked with api call which i used in sample application still i'm getting the data for that url but i didn't specified in ngsw-config.json file.
I can't unregistered my old service worker and create new service worker. In chrome developer tool i unregistered that service worker and again reload my application but still i'm getting the old data.
Angular version: 6.0.2
Browser:
- [ ] Chrome (desktop) version
For Tooling issues:
- Node version: 8.9.1
- Platform: Windows
Is it possible to launch a Chrome app without having the Chrome Browser appear?
In other words can the browser run in the background and launch a chrome application?
Yes, if the app creates its own window then just run it from the Chrome app launcher or make the shortcuts on desktop / startmenu / taskbar: open chrome://apps/ page (it can be opened from the new tab page), right-click the app, click Create shortcuts.
To run the app using command line use the app ID (to get it first create a shortcut as described above and simply copy the command line from the shortcut's parameters, or you can copy it from the webstore page of the app), here's a Windows command line using start which automatically finds the installed Chrome executable:
start chrome --app-id=pelimflkpjiicnajdjcmekpioacmahkh
P.S. The app must be installed in the browser.
I am trying to install App using App Manager in Firefox OS device. But my problem is I am unable to push any of the apps which are published on MarketPlace. It show that
The webapp manifest isn't a valid JSON file: SyntaxError: JSON.parse:
unexpected character at line 1 column 1 of the JSON data at:
https://marketplace.firefox.com/app/pacman-canvas can't be opened
So can anyone suggest some way to push the app to my device using App Manager only?
It's pretty easy. On the Marketplace page (in Firefox desktop) open the marketplace page for the app. Then open Devtools and select the Debugger. In the debugger, break in file iframe-installer.html, on this line:
installPackage(e);
Now click the 'Free' button, the debugger will break on this line. In the console you now type:
e.data.data.product.manifest_url
This will give you a URL. If the URL is located at someone else's webserver (like Pacman), e.g. http://pacman.platzh1rsch.ch/pacman-canvas.webapp, you can (in the App Manager) click 'Add hosted app' and paste the URL. However you will need internet on the phone the first time you use the app (because its hosted app).
If the URL is a Mozilla URL (https://marketplace.firefox.com/app/etc.), you can open the link in your browser. Open the file. You now have a JSON file in which you need to look for the package_path key. F.e. for Recorder it's
"package_path": "https://marketplace.firefox.com/downloads/file/258677/recorder-1.1.zip"
You can now download this ZIP file, unzip it in a folder, and add the folder as a Packaged app.
For apps in the marketplace, you best solution for getting them on the phone is to just use the marketplace app. That said if you own the app in the marketplace you should be able to look at the manifest url of the app using the edit listing marketplace button. If this is a hosted app you can you use this manifest url in the add hosted app entry box within the app manager to add it and then push it to phone. On another note you can debug the system apps by using the procedure described here:
https://developer.mozilla.org/en-US/Firefox_OS/Using_the_App_Manager#Debugging_Certified_Apps
I have a Google Drive app, which is registered as my default opener on Google Drive. This works perfectly fine when opening files using drive.google.com - When I open a file with my App, the app gets given permission to open the file and I can see that in the drive.google.com web interface.
However I recently tested this on a chromebook, and when I open a file using the Files app, I get sent to my app, however it gets a 'File Not Found' error. When I check the permissions for that file, my app hasn't been given access to it.
If I open the file using drive.google.com and then try opening using the files app again, it works since my app has been given access to the file when I opened it using drive.google.com
Seems there is a bug in the Files app on Chrome OS here, where it doesn't set the permissions to give the app opening the file permissions to access it, whereas the web interface does that correctly. Has anyone else run into this and/or should I report this as a bug to Google?
Using ChromeOS 5116.115.4 + Chrome 33.0.1750.152
This was indeed a bug, and it's fixed in the upcoming chrome 34: https://code.google.com/p/chromium/issues/detail?id=332332