I have made iOS apps in the past but this is my first desktop mac app. We have a strange problem. I build for archive, validate it and send to test users. The app loads but doesn't get past the splash screen for those users. I tested with two non-developer users on my machine (same machine as development) and the same thing - it stalls on the splash screen in both Lion and Mtn Lion. For the two developer users, it is working fine.
Now something tells me there's a permissions or signing problem. But if that's the case, wouldn't the app not load at all? The other thing is that we are writing to the Library/Application Support folder. For these test users all the files that are supposed to be there are there - so the app is launching and writing.
Does this problem sound familiar at all or any tips on how to diagnose?
Related
I am developing a web application with Meteor and WebStorm as IDE.
This application can be called from a PC, a tablet or a phone, which does not pose a problem of execution since it is called in the browser.
On the other hand problems appear, which are due to the size of the screen and the positioning portrait or landscape.
To test, a solution is to deploy the app, open it in the phone browser and see what works or does not work. A bit heavy ...
Is there a method to test a web application on a device connected to the development PC, through WebStorm, can be with an added package, or with another tool
Any leads or ideas would be welcome.
Thank you for your answers
YC
I have had a similar issue, I used Ghostlabs (https://www.vanamco.com/ghostlab/), to test different screensizes simultaneously. You will need to have physical devices present and connected to your development machine.
Saucelabs(https://saucelabs.com/) in my opinion is an extension of Ghostlabs, with the advantages of using the cloud.
One other tool I would recommend is Browser stack (https://www.browserstack.com/) it gives similar benefits as Saucelabs.
These tools I find are very effective for cross browser testing too.
I've created a Mac App for Mavericks that uses MapKit. It works fine during development and testing on Xcode 5.1. Now I'd like to submit it to the App Store and I need a Distribution Profile which I've created successfully. Trouble is, as soon as I add it to my project, the app doesn't run anymore - it crashes every time without fail with this error message:
When I change back to "no provisioning profile", or to the profile that Xcode created during development, the app runs again.
My question: Is this expected behaviour, or will the app be rejected by the review team? I know that iOS apps don't run with their distribution profiles, but I'm new to Mac Development. Any insights into this way too complex topic are appreciated!
My app was approved - and the crash was indeed no issue for the app review team.
I had a chat with Apple about this who were kind enough to call me back and explain the issue. Looks like this phenomenon is "kind of" expected behaviour: Mac Apps may or may not crash when run with a Distribution Profile.
To avoid this problem, we can add both a Development AND a Distribution Profile to our app, without one having to replace the other. This was news to me. Had I however opened my tired eyes a bit wider I would have perhaps spotted the little disclosure triangle myself:
Perhaps this helps those with the same issue.
I am developing apps (for MAC) which will NOT be hosted on the app store.These apps will be installed by dmg file. Can someone please confirm my assumptions?
Even if I dont sandbox the apps, app will still work on OSX 10.7 and above (provided see point 2 below)
If the security setting is "Mac Appstore and identified developer", in a non sandboxed scenario, user needs to right click and open the dmg file instead of double click it and installer can install apps to Application folder. Once installed applications can -
-Interact each other
-Access files
Yes, out of the app store apps don't have to run in sandbox.
The security setting has nothing to do with how your app is installed. If you build a installer (Xcode can do it for you) or you if you send the .app bundle in a dmg to be dragged into applications folder is a thing of your choice. An app that is not running in sandbox can interact with any other app and with any system resource, only limit is user permissions. OS X is still Unix and the fact that app store has rules about sandbox doesn't change the world out of app store.
I am working on developing a Mac application that has an in app purchase. I have done this before on iOS, but I cannot get it to work with the Mac app. After doing some research it looks like I will have to get and validate a receipt from the Mac App Store before this will work.
I believe that I have followed the steps to do this correctly,
1.) Build the app in Xcode.
2.) Launch the app through finder
3.) When prompted sign in with a TestUser account created in iTunesConnect
4.) The app closes with the error message
“AppName” is damaged and can’t be opened. Delete “AppName” and download it again from the App Store.
When I open up the bundle though I do not see the _MASReceipt/receipt folder and file - and I am still getting invalid product identifiers from StoreKit.
These steps seems to work for me the last time this happened:
Log out from Mac App Store.
Force quit storeagent and softwareupdated processes.
Try double-clicking the app to start it again.
I've been building and deploying apps for several months now and am aware that provisioning can get a bit sticky at times. But my current situation is particularly unusual.
I can attach my development device and build and run the app on it through Xcode. If I archive it for Ad-Hoc Distribution as an ipa file, I can also successfully load it onto a distribution device via iTunes. However, running it on the device causes an immediate crash: it opens then promptly closes.
There are no permissions errors during the iTunes load, and this issue presents so far on 3 distribution devices, including the same device that it successfully runs when sent via Xcode.
For the life of me I cannot figure out what is going on; in the past, if there was a misplaced profile or a device not added to the profile, you'd get a simple permissions error during the iTunes sync. I've never seen it successfully transfer to a device with no errors, but then crash. I'd love some suggestions as I've been working with this for 2 hours trying to track it all down.
All devices are in the provisioning profile and I reloaded the profiles in XCode to make sure they were current. I also reloaded the ad-hoc profile in iTunes to make it was current.
I've had a similar experience with expired provisioning profiles: dev build of an app opens then immediately closes when run on a device. Double check that all profiles installed on the devices are current.