I try to add either a packaged or hosted app into app manager on firefox 30. I've verified that the hosted app works on my handset (obviously I have no way of testing that the packaged app works without installing it via app manager, which isn't working). The app then does not show up in the list of apps in app manager (which is empty), nor does firefox display any error messages either as alerts or logs in the console. I went on a hunt for logs around my filesystem, but I couldn't find anything. I am on OSX 10.9.
I just had the same issue, appeared that I was running Firefox without write rights. Starting FF with sudo resolved the issue.
Related
We have an app with custom URL scheme, let's say "com.company.app". In a javascript file, we invoke the app by window.location = "com.company.app://";. If the app is not installed, Safari throws the erorr "Safari can't open the specified address..... doesn't recognise Internet addresses starting with 'com.company.app'". This happens only on Safari and not other browsers.
Chrome and Firefox don't throw any errors in similar situation i.e they know that com.company.app is a protocol handler and if the app isn't installed, they don't throw any errors and just continue execution.
Safari thinks that com.company.app is a website and tries to load it instead of trying to open the app.
Note that this happens only when the app is not installed. Works fine with Safari if the app is installed.
I've also tried restarting browsers, restarting machine, removing default app using "Default Apps" app etc.
Safari version: 12.0 (xxxx)
macOS version : 10.14.x (Mojave)
Currently i use TestFariy for beta app distribution, which works some of the time.
Reading its apparently possible to build own .ipa file place it on a web server and using safari to download it onto devices.
I have been having a play but don't seem to be able to get it working.
We have a standard developer license.
I archived app and included the manifest file.
I placed both files onto the webserver along with a html file that basically provides an event to download the file
Install App
Now in safari on devices when i hit the button on the link i get the popup asking if i like to install, i select yes and i then just get a new icon with 'Waiting' and it hangs here, no error messages just stays on 'Waiting'.
Anyone any ideas?
Thanks
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.
I have the app for the Mac App Store and I faced with the following problem. Version 1.1 is already in the Mac App Store.
If I change a version of the app to 1.2 and try to run it with a test account I receive the message:
The app is damaged and can’t be opened. Delete the app and download it again from the App Store.
The Console shows entry:
Exited with code: 173
I return previous version number 1.1 back, the app starts. I tried to send the app to my colleague. It runs normally. I tried to remove all same binaries from my hard drive. It doesn't help.
I had the same problem before and I even submitted the app in that state to the App Store. It was successfully approved. Now I can run 1.1 with a test account, but I can't run 1.2.
How to solve this issue with App Store?
a return code of 173 means the store receipt validation fails.
since you only bought 1.1 from the store, the receipt is for 1.1 and not 1.2.
SO if you change the app's plist to 1.2 the validation fails... receipt 1.1 vs. app 1.2
Try this (it worked for me) :
Open terminal, and type :
cd /Applications
sudo chown root Clear.app
sudo chmod 777 Clear.app
then open Clear app.
If you trust the people from whom you are downloading things you can bypass the warning by adjusting your ‘Preferences > Security & Privacy’ to
Allow applications downloaded from: Anywhere
I have create in sandbox, an app which use a helper to start at login, as presented here.
It works ok, but the next messages are logged in the console:
lsboxd[1560]: Not allowing process 15208 to launch "/Applications/SandboxApp.app/Contents/Library/LoginItems/SandboxHelper.app" because it has not been launched previously by the user
lsboxd[1560]: Not allowing process 15208 to register app "/Applications/SandboxApp.app/Contents/Library/LoginItems/SandboxHelper.app" for launch.
I see that this messages are about the helper, but I don't know what to do, to prevent them.
My only concern is that Apple may reject the app because of this messages.
Is someone who prevent the raise of those sandbox messages, or is someone who sent an app, which raise sandbox messages, to Apple and was accepted on Appstore?
See http://blog.timschroeder.net/2012/07/03/the-launch-at-login-sandbox-project/ - according to this it is a code-signing issue that probably won't be an issue with the AppStore build as the AppStore build gets resigned.
This should work in the final build. According to Apple Documentation (Section “Launching Helpers with Launch Services”):
Launching Helpers with Launch Services
A sandboxed app is allowed to
launch a helper using Launch Services if at least one of these
conditions has been met:
Both the app and helper pass the Gatekeeper assessment. By default
that means both are signed by the Mac App Store or with a Developer
ID. Note: This does not include your development ("Mac Developer") or
distribution ("3rd Party Mac Developer Application") signing
identities.
The app is installed in /Applications and the app bundle
and all contents are owned by root.
The helper has been (manually) run
at least once by the user.
The first and/or second one should cover your case when your app was installed through the Mac App Store.