I'm trying to install an unlisted webextension on Firefox for Android from a website but it keeps blocking it, even though it is signed (preliminarily reviewed).
I can only install it, by going to Mozilla's website, downloading it and installing it immediately. Not even if I run it from a file manager.
Do I need a custom certificate or something?
Thank you.
Source:
https://developer.mozilla.org/en-US/Add-ons/Distribution
Related
After downloading Termux from the Google Play store, FDroid, and Github, I got the error
Unable to Install
Termux was unable to install the bootstrap packages.
Check your network connection and try again.
I looked through Github and found this this reply saying to try to connect to http://termux.net/bootstrap/ in a browser. I tried with the phone I'm trying to put Termux on (Galaxy s5 with Android 6.0.1) and got a response saying 'connection timed out'. I tried on my desktop which is on the same network, and got the same response. I made a simple python script using the requests module on a Replit server and got the same response with error 522.
It seems like the Termux.net website isnt working for some reason, maybe because of a WiFi setting that has to get changed? What else do I try?
Issue is that old links for bootstrap package for Android versions 5 and 6 are not available anymore, for example domain https://termux.net is down and you can not access it.
You can fix this issue by following this wiki:
https://github.com/termux/termux-app/wiki/Termux-on-android-5-or-6
You can install artifacts from this link:
https://github.com/termux/termux-app/actions/runs/2619084610
*Zipped APK file termux-app_v0.118.0+605dd6c-apt-android-5-github-debug_armeabi-v7a can be downloaded from this link:
https://github.com/termux/termux-app/suites/7230045376/artifacts/289921940
*Note: Direct APK link will only work if you are signed in with your GitHub account
works great, just download the apk from link above and install
Thanks nexayq, just make sure you allow installation from unknown sources in your android settings.
Tested on two phones the ones with armeabi64-v8a works to know this just download device info hw from playstore
I have a private xpi file signed by the Add-on Development Center. I would like to install this on android's firefox-beta (firefox-beta 79.1.0-beta-1). However, when you install it, the download is completed, and when you "Open"
The file could not be opened.
Is displayed and installation is not possible. If you do the same operation with firefox 68.11.0 on android, xpi will be installed successfully.
Originally, I wanted to do remote debugging, and I needed firefox-beta or nightly for remote debugging, so I'm trying to install xpi on beta.
Also, there seems to be a way to make html, download xpi with a link from there, and install it, but with this method,
firefox beta cannot download this file type
It will be displayed. (it is japanese message.)
Please tell me.
I've successfully connected Firefox for Android to my desktop Firefox, I'm able to debug pages, and even install applications.
The problem is that installed applications do not start. And in result I can't debug them. Even worse, that now I'm unable to delete installed app from device, there is no such button, and my app is not listed among android apps like those which are installed from Firefox Marketplace.
Does anyone know how to deal with that, or it is now working yet?
Ubuntu 14.10 x64, Firefox 31.0, Firefox for Android 31.0 beta (used stable with the same result), Android 4.4.4 (CyanogenMod 11)
Unfortunetely you cannot debug installed Firefox OS apps on Android phone via Firefox for Android. You can only debug web pages in Firefox for Android via remote debugging. https://developer.mozilla.org/en-US/docs/Tools/Remote_Debugging/Firefox_for_Android In case of Firefox OS app, you have better use App manager or simulator. Of course, if you have Firefox OS phone, you can do this via remote debugging between Firefox OS phone and your desktop.
Here are the generic instructions (after which I'll address your specific issues):
Install mozilla-apk-cli using NPM:
npm install -g mozilla-apk-cli
Use it to generate a "debuggable" APK for your app from either a source directory or a URL to the mini-manifest:
mozilla-apk-cli /path/to/source/dir/ arbitrary-name.apk
mozilla-apk-cli http://example.com/path/to/mini/manifest.webapp arbitrary-name.apk
(Context-click > Inspect Element on the "Free" button in Marketplace to discover the mini-manifest URL for an app in the Marketplace.)
Install the APK on your Android device:
adb install -r arbitrary-name.apk
Launch the app on the device. Look to the notification area for a notification about which port the remote debugger server is listening on. Forward that port on your desktop, f.e. if the port is 12345:
adb forward tcp:12345 tcp:12345
Go to Web Developer > Connect… in Firefox on your desktop and connect to localhost at the forwarded port. Commence debugging!
Notes:
Use Nightly builds of Fennec for the best experience.
Bug 929382 tracks WebIDE (née App Manager) integration.
File bugs on problems you encounter!
Now, regarding your specific issues: It sounds like you've made it past app installation but are stuck on launching and running the app. How are you launching the app? For example, are you tapping the app's icon on Android's All Apps screen? And what do you mean when you say that apps "do not start"? Do you mean that nothing happens when you launch the app, or does something happen (f.e. a splash screen appears, perhaps followed by a white screen), but the app itself doesn't appear?
It would also be useful to know the manifest URL of the app you're testing, if it's a public hosted app; or get access to the source code, if it's a public packaged app!
Finally, note this related (identical?) question: How to install packaged app on Firefox for mobile?. I copied the generic part of this answer from it, but presumably they should be consolidated into a single answer (modulo the troubleshooting info, which is specific to the problem you're encountering).
I need to test my Android app for playing flash objects in the WebView.
At first I didn't need to test it on the emulator since I have an actual device (Android 2.3.7) but since users have been reporting issues about the app on Android 4.0 (Ice Cream Sandwich), I want to test it now in the emulator.
First I tried to install the Android Market using
adb install androidmarket.apk
After installing it, it just closes when I open it so I downloaded the Flash Player apk and installed it the same way.
adb install flashplayer.apk
So I tried the app but still no flash is playing.
Then I read somewhere that I should be installing the Adobe AIR instead. I installed the apk using the same approach
adb install adobeair.apk
Tried the app again but still the same. Just the blue box with a question mark appears.
Any idea how to test Flash videos on the Android emulator?
EDIT:
I've also tried
adb -e install -r adobeair.apk
with the same result.
First I tried to install the Android Market
The Android Market/Google Play client is not licensed for distribution and use this way. You cannot obtain a legal download of this APK from Google.
so I downloaded the Flash Player apk
Please point to where you can get an authorized download of this APK from an official Adobe Web site.
Then I read somewhere that I should be installing the Adobe AIR instead. I installed the apk using the same approach
Please point to where you can get an authorized download of this APK from an official Adobe Web site.
Any idea how to test Flash videos on the Android emulator?
Even if there were legal downloads of the required APKs (and I am not aware that there are), Flash/AIR depend heavily on hardware acceleration and cannot work in today's emulator.
Just a several days before, on the site:
http://download.macromedia.com/pub/flashplayer/installers/archive/android/
You could have found many APK packages with various versions of FlashPlayer for Android. They even have been successfully installing on the emulator - although I actually DONT KNOW if they work properly (I had no point in running anything..).
As of today (=2012.11.18) they site is almost down, but you can still downlaod the packages, for example:
http://download.macromedia.com/pub/flashplayer/installers/archive/android/11.1.115.27/install_flash_player_ics.apk
edit: I've just found the proper site:
http://helpx.adobe.com/flash-player/kb/archived-flash-player-versions.html
edit2: nope, it installs but does not seem to work. I've just tested http://www.adobe.com/swf/software/flash/about/flashAbout_info_small.swf on emulator and empty black page showed up.
You can download the APK you need for all flash versions for Android 2.x and 3.x, even for Android 4.0 at the following location:
Archived Flash Player versions
Just scroll down a little bit
I have developed an application using Android SDK 1.5, application works well on Android Simulator.
Now, I am trying to install application on actual device. I don't have the Android device. So, I am going by OTA way.
For this, I have generated the self sign keystore using keytool utility.
And, using Eclipse's "Eclipse Signed Application package.." option I have generated the signed .apk file and moved it to my web server.
Also, i added MIME type on web server for .apk.
But, when I am trying to download and install the same application on device, application get downloaded and it also prompts for permission. After thag when I click on "Install", it fails with error Application Install Unsuccefull.
Interestingly, I test this url on simulator browser, and it worked perfectly well and application get installed successfully.
Even, I checked that, SDCard is there on device. Settings -> Applications and "Unknown sources" option is alos checked.
Am I clear to you all?
Any Idea what may be going wrong here?
Thanks and appreciate your response,
S.Satheesh
What happens if connect the phone via a USB cable and install the application using the adb install command? Testing this will allow you to determine if the problem is with the package or the over the air update.
Also, you could try running adb logcat to view the logs from your phone after the failed install as this should show you what the problem is.