missing package product

Thanks --All in all I just can't believe what a piece of **** Apple really is. Thousands upon Thousands of apps are getting scammed out of Digital goods every day (which is a direct correlation to real money to us and several others) and their response is just go figure it out yourself, here is some documentation'. This is like PayPal not securing their transfers and you being able to buy things online and get free eCommerce. For this big of a company to just 'let developers' figure out how to secure their apps makes me lose so much respect for them. *** you apple.

I think the problem aren't Apple in this case.From one of your own post:No all you have to do is jailbreak the phone and get free in app purchases plug in and then you can get anything free that's not server verified before adding the purchase to the user account.If a phone are jailbroken, you can request on a app the purchase. Now, in Jailbreak, you have installed an app who when request a purchase, they doesn't send it to Apple, and send to your app an OK.I understand the problem here are the Jailbreak itself. Apple try to avoid it, but, there's a lot of people who try to mantain it.There's a lot of people who are scammed every day because Jailbreak, in form of downloads of the app without payment, or in-app purchases without payment. At first case, you cannot verify, because, if an app doesn't need a server for work, these app can open and work correctly even if it's downloaded from ***** repository.Also, i doesn't know how you can verify the app purchase itself, I think these are more difficult who verify

That is correct. El Capitan, Xcode 7, iOS 9, Watch OS 2 are all beta, pre-release, developer preview, not ready for prime time, not released yet. You cannot build production code with them until they are officially released.If you need to go to production before they are released, then you need a completely separate stable production environment for your builds. This has always been the case. It would make no sense whatsoever for Apple to allow production code to be built with buggy pre-release tools.

Going to production with a build from the beta toolchain is obviously a bad idea. But that is very different from outright disallowing Xcode < 7 to run on El Capitan.I know in my case we have a stable build machine, but several developers are on the beta tools so we can get a jump start to finding/fixing bugs. In our case this change does nothing to protect against builds being submitted with beta tools (since we wouldn't have done that anyway) and makes active testing against those tools that much less likely to get done properly. Seems like a lose-lose to me.

Since 10.11 Beta #2 all Xcode 6.x versions will have the no go sign on their icon and won't launch, stating incorrect OS version.However ... this can be easily bypassed by locating the Xcode.app in Finder under Applications. Right click and Show Package Contents. Browse into Contents/MacOS folder. Double click the Xcode executable file to launch Xcode (it will bring up a Terminal window - don't close this window as it is the Xcode process).So yes, it does work, but only if worked around OS X's version compatibility check.Not a big deal really. There's far worse issues in beta #1 so do upgrade. 😉

You wrote: delegate call didUpdateLocations uses beginBackgroundUpdateTask() / endBackgroundTask()I do background track recording but I don't use background tasks. I just allow the location manager to use deferred location updates, and let the app get suspended if the OS so desires. Next time the device wakes up (if the user hits the Home button or some other event), your app will get the location updates for the whole period all at once.The phone has no way of knowing whether it's on the ocean or not. If it has a view of the GPS satellites then tracking should continue. Do you see degraded accuracy on the last few readings before it stops recording? Perhaps it is losing the satellites?I would also recommend putting a whole bunch of logging in your location handling code to make sure you aren't inadvertently discarding valid location updates due to a bug in any filtering code (discarding because they're too old, insufficient accuracy, or whatever).

Even if it works using the above mentioned hacks, it leaves your system in an unsupported configuration. Personally there's no way in **** I would ever put my development platform in that kind of state. It's my bread and butter.My suggestion is if you want to kick the tires on El Capitan, do it on a different machine, or on a completely separate boot drive. You do *not* want to mess up your production environment.

It's a bug then.One should never be able to submit production code using any kind of beta.

{ CatalogURL = https://swscan.apple.com/content/catalogs/others/index-10.11seed-10.11-10.10-10.9-mountainlion-lion-snowleopard-leopard.merged-1.sucatalog.gz; DisableSeedOptOut = 1; LastAttemptSystemVersion = 10.11 (15A204h); LastBackgroundCCDSuccessfulDate = 2015-06-23 18:04:34 +0000; LastBackgroundSuccessfulDate = 2015-06-23 18:04:34 +0000; LastFullSuccessfulDate = 2015-06-23 18:35:03 +0000; LastRecommendedUpdatesAvailable = 0; LastResultCode = 2; LastSessionSuccessful = 1; LastSuccessfulDate = 2015-06-23 18:35:03 +0000; LastUpdatesAvailable = 0; PrimaryLanguages = ( en ); RecommendedUpdates = ( ); SkipLocalCDN = 0; }EDITED: because initial copy/paste lost the long URL at the top for some reason.

App submissions tend to be about the code submitted, not the OS that generated it. XCode is the focus here and the store rejects any code that comes from Beta XCode version (having done that by mistake more than once,). Im not sure they care about the OS part, as it doesnt leave trails in the code that seem to care about. Today you can submit on a range of OS X versions, basically anything that runs XCode 6.x and meets the other code requriements.In the past they have always had both a GM version of XCode for each OS beta, to support submissions and other testing. With XCode7, I have not seen the normal words about no submittal using the beta that normally is there. Maybe its there and I just missed it. Do we know for sure that current XCode7 cant be used for submission?

Xcode failed to download the symbol files from http://adcdownload.apple.com/Developer_Tools/watchOS_13S5255d/Watch1_1_13S5255d.dmg.I was successful to launch my watchOS app by following steps.1. Download the symbol file installer for 13S5255c from http://adcdownload.apple.com/Developer_Tools/watchOS_13S5255c/Watch1_1_13S5255c.dmg.2. Create directory ~/Library/Developer/Xcode/watchOS DeviceSupport/2.0 (13S5255d)/Symbols3. Mount the DMG and open Watch1,1.pkg.4. Change the destination directory to above directory. (DO NOT install to default location! OS X will be destroyed!)5. Install symbol files.6. Open project on Xcode 7 beta.7. Disconnect and connect iPhone.The symbol files may not match with the actual system. But I'm not interested in system symbols.