How to add FOREGROUND SERVICE PERMISSION in service tag in manifest file? - foreground-service

In android version 9 when i am uploading an image application is kill , but image is uploaded successfully,
in other version it works fine

Related

Is transcrypt supposed to run from the local filesystem?

I've installed Transcrypt, compiled the Hello Solar System demo, and run it as instructed using the python web server.
However, I was also able to run the hello.html file directly from Chrome on Windows 10 ... once. Subsequently it refuses to run - the buttons appear but clicking them does not update the text.
------- EDIT ---------
Thanks - CORS is the problem - the browser must connect to a web server, not a file on the local filesystem.
You've probably run into a security policy of Chrome called CORS. Start a webserver from the directory where your html file is, using python -m http.server, and browse to localhost:8000. In your browser window, click on the html file and things should work.

Can't View FTP Directory in Google Chrome

I just upgraded to Google Chrome v73.0.3683.103 and I am now unable to view FTP sites in Chrome. Instead of Chrome loading the FTP directory listing in the browser, it downloads a file named download which contains a directory listing.
How do I get the ability to view the FTP directories directly in Chrome back?
I have tried going into Internet Options > Advanced and clicking on the "Enable FTP folder view (outside of Internet Explorer)" but, that didn't seem to do the trick.
In-browser FTP was deprecated back in v72. I hadn't updated Chrome in a few releases. I have rolled back to v71 until I find a better workflow substitute
DETAILS: https://developers.google.com/web/updates/2018/12/chrome-72-deps-rems

Uploading remote image to webpage using Chrome File Upload Dialog

How do I upload an image that is located on the web to a different webpage without manually downloading and uploading it?
Example: Using the Chrome browser I want to upload the Wikipedia logo onto this post. I copy the URL of the image, https://www.wikipedia.org/portal/wikipedia.org/assets/img/Wikipedia-logo-v2.png, and on this page I click Image and paste the URL in the Upload File Dialog but then I get an error.
Screenshot of error at Chrome's Open File Dialog:
I used to be able to just paste the URL of a remote image and it would upload it as if it was a local file (probably downloading it to the Windows temporary internet files folder).
I'm not sure what happened, but when I try this now I get an error stating that the "The RPC has failed and did not execute" (translated from Dutch). Searching the internet for this error related to Chrome uploads gave no results.
Is my computer being weird, or have I been using a functionality that shouldn't have worked in first place?

Install firefox os apps available on Marketplace using App Manager

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

Open With from Chromebook file app doesn't work

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