Re: 2 itunesconnect questions
Years ago I used my real name. I was very new to cocoa (this is like 2002) and asked some dumb questions. I got flamed to death. I began using a man's name shortly there after and dumb questions did not receive even remotely the same hostility. (Admittedly some though) I started using that fake name in all correspondence and people stopped asking for refunds over a minor bug with a quick workaround. Perviously, I'd get a support request, they'd see a woman's name in the signature and the reply from them? "doesn't work I want my money." Immediately after playing a game of remmington steele (2 pts if you get that) that type of crap stopped. People would trouble shoot, follow instructions, and act with a degree of dignity. (Albeit in many cases minimal at best). I was able to quickly find work arounds, then implement a fix and release an update. Where previously getting enough information to even figure out what had happened was like pulling teeth... wisdom teeth, no pun intended. Some time later I decided that playing boy so people would listen and treat me with even the most minimal respect was B.S. That's why the meaningless name in my email even though by and large I do not use a pseudonym anywhere else in the world. My name is April. You can refer to me as April if you so desire. And yes, believe it or not, sexism still exists. And honestly with things like the Dr. Pepper commercial I'm not really sure if it's getting better or worse. Anyway until you just mentioned it, it never even dawned on me that I was still "hiding" on this list. April. On Nov 11, 2011, at 3:50 PM, Conrad Shultz wrote: > P.S.- Just a little suggestion, but would you consider posting messages > without using a pseudonym? Being able to refer to people by name > instead of the "OP" feels much friendlier and more natural. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: 2 itunesconnect questions
Hmm It's difficult to argue with numbers like this, and of course I am guessing that a noticeable divot in sales really isn't there unless I actually do write the next angry birds... Of course based on their ratio, I'll have to write another 23 applications before I have a hit of that magnitude. Another option I suppose that is a little more difficult to deal with crack wise, is release all applications on the shareware model. Free limited version with an in app purchase to activate. I've always done all verification on my server and already have the back end to handle all of that with next to no extra code so anyway... That said, I would never be foolish enough to think a "pirate" is a potential customer. A pirate would spend 6 months cracking an app before they'd spend $10 to buy it. It isn't the pirate I'm concerned with. It's the on the line, "I'll buy it if I can't find a hack" type. You know, the type that likes software "protected" by Kagi. On Nov 11, 2011, at 4:25 PM, Conrad Shultz wrote: > On 11/11/11 2:02 PM, Development wrote: >> Well your average dolt that jailbreaks and knows absolutely nothing >> about it would be blockaded. It's the folks that have hex editors and >> the time to figure it out that will find it easy. Which is still a >> little too much for many JB'ers. Besides, I want to see it broken so >> I can figure out how to stop it from happening in the next point >> release. That said... On my mac software I have a library I've >> written that makes cracking more difficult than using a hex editor >> and changing some bools. Specifically it uses a non MD5 hash to >> detect the slightest change in the binary, libraries or data files. >> Thus far, recompiling alone with absolutely no changes to the code >> will fail the hash check. Its been fairly successful. But I don't >> really understand code signing that well. so I am curious if such a >> hash would be possible on an iOS app. My understanding tells me that >> it would not work. The problem being of course that the hash is done >> after the app is built, archive builds preclude the inclusion of an >> after the fact data file. > > (Insert obligatory statement about cryptography being hard here.) > > Setting aside all the technical issues, do you have evidence that > jailbreak piracy is a large enough problem to justify you doing all this? > > For one, while I don't have a percentage I'm quite certain that it is a > minority of phones that are jailbroken. I run with a pretty tech savvy > crowd and I know only _one_ person who has jailbroken their phone, and I > am fairly confident that techies are more likely to go through the > trouble. (How many average users have the faintest idea of what it > means to "jailbreak" a device?) > > Jailbreaking is probably more prevalent in countries and cultures with > less of a tradition of paying for software. But this leads to the > second point... > > From your standpoint you (presumably) really care about converting > would-be software pirates into _paying customers_. If they can't use > your app on a jailbroken device yet don't buy it legitimately, you > haven't accomplished anything economically worthwhile. In fact, you may > be worse off because you lose the (admittedly small) possibility that > the would-be pirate will show off your app to others who might in turn > become paying customers. > > So, your calculus ought to be something like: > > (# users with compatible devices) * (% with jailbroken devices) * (% > interested in your app) * (% unable or unwilling to circumvent your > protection) * (% who will purchase your app when confronted with copy > protection) * ($ price per sale) > (increase in legitimate sales that > could be obtained by devoting development resources to product > enhancement, marketing, support, etc.) > > Let's suppose that 250M compatible devices have been sold, with 150M > distinct users (assuming that there are many people who have replaced > devices or own iPad with an iPhone, etc.) Suppose 10% are jailbroken, > which is what some cursory Googling turns up. That gives us 15M > candidate users. > > Now, unless you are writing Angry Birds, it seems unlikely that you will > appeal to any more than 1% of the user base. That leaves 150K users. > Maybe 80% are unwilling to circumvent your copy protection, leaving 120K > users. Now the kicker: how many are then going to want to actually buy > the app? Maybe 5%? That puts you at 6000 users. > > So with these admittedly crude guesstimates, if you could gain even 6000 > users (out of the 135M non-jailbroken user base postulated above) by > devoting your time and energy to anything else, you'd come out ahead. > > Do you think that is not possible? Do you disagree with the analysis? > (I'm not asking rhetorically; I have based my own decisions on such an > analysis and would welcome criticism or clarification.) > > > -- > Conrad Shultz > > Synthetiq Solutions > www.synthetiq
Re: 2 itunesconnect questions
On Nov 11, 2011, at 7:14 PM, Conrad Shultz wrote: > On 11/11/11 4:59 PM, April wrote: >> Years ago I used my real name. I was very new to cocoa (this is like >> 2002) and asked some dumb questions. I got flamed to death. > > Greetings, April. I regret that you were mistreated in the past; I am > confident that will not occur now. > > Anyhow, did you get a chance to try the couple suggestions I tossed out > in previous messages? > > I remain a little hazy on how your project got into this state. I > understand that you manually set build architectures, but vis-a-vis > creating a universal app, did you: > Actually I had a long existing project that I start working on in 4.1 before the release and then 4.2 when I started icloud support up until now. I've hit multiple delays and setbacks due to adding features out of fear of 1 star ratings due to "It's useless cause I cant..." Even though many of the features are simply moronic on a touch platform. For instance the ability to draw freehand on an iphone in an app for serious use. Anyway all I did when I started working in xcode 4.2 was set the base sdk to 5.0. I never changed the deployment target away from actually, 3.2. Later I implemented ARC but only changed the deployment target to 4.2. And this project was originally poorly implemented in that there were 2 separate projects, 1 for iPad, 1 for iPhone/iPod. So I brought all of the code under one roof and used a simple ISIPAD definition (a macro for the interfaceidiom check) to figure out what should do what. not that that matters. Anyway. In xcode 4.1 the arch had been armv6/armv7 and I never really bothered to look at it again after installing the final xcode 4.2. I built and ran.. according to the bundle version script's last incrementation at release 2673 times over a 5 month period. Installed at least a dozen or more adhoc builds via itunes to check some built for release things. never got an actual error... though I was ignoring warnings in the build window. Won't do that again. so last night I was surprised. Like I said stack overflow had an answer, but since starting this thread I now understand the problem, thanks both to you and others. Had I changed the build target to 4.3 I'd have never seen the error. But because I was trying to maintain some degree of backward compatibility I got the error. I did manage to get it submitted with armv6/armv7 compatibility. version 3.1 may not support armv6. I'm still contemplating that. mostly I hate the "What about us" support emails. The ones I got a few hundred of when I updated a mac app to intel only, app store only. So I guess, technically if you can consider it converting rather than uh... Conforming it to xcode 4.2's available settings until it built, I manually converted it. This is embarrassing to admit, but at the time I was so wrapped up in getting this app working, chasing bugs and trying to have it submittable by the GM seed (which I missed by a damn site.. thanks useless assembly language class I will never use in life.) that I didn't really give much thought to reading the "switching to" docs. > a) Start a new Xcode project, configured to be universal; or > b) Convert an existing project using the universal conversion feature; or > c) Convert an existing project by hand? > > I ask because I remember something in the docs about how the > migration/conversion feature does more than just change the target > platform and add a couple nibs, and that we shouldn't try to convert > projects manually. If this is what you attempted then it seems possible > that there are other magic flags that need configuration. > > Also, since this topic now seems to be well within the tools domain, you > might get good feedback on the xcode-users list as well. > Well with the app submitted and my motivation to learn cocos2d low... Thats a long story that for the first time in 10 years has me seriously considering trying to sell a project rather than complete it. Anyway, I suppose it's time to catch up on the 4.2 docs and "switching to" notes etc. I have 4 apps, two on the store, two in development, that need updating/completion. Plus the app this thread relates too already has a full plan for 3.1 laid out as well as around 500 lines of commented code. (Things I skipped in order to get it out the door.) It would be nice to not have to ask another dumb question each time I start work on one of these. Besides, even with months of 8+ hour days deep in the code, I just know that the complete failure of iBetatest.com to produce anything useful, means I've missed something somewhere in my testing and that of the 1 person that ever ran the app when I asked them to, and I am going to have to fix a crash
Re: 2 itunesconnect questions
On Nov 14, 2011, at 5:32 PM, Conrad Shultz wrote: > On 11/11/11 9:50 PM, April wrote: >> Actually I had a long existing project that I start working on in 4.1 >> before the release and then 4.2 when I started icloud support up >> until now. I've hit multiple delays and setbacks due to adding >> features out of fear of 1 star ratings due to "It's useless cause I >> cant..." Even though many of the features are simply moronic on a >> touch platform. For instance the ability to draw freehand on an >> iphone in an app for serious use. > > As a user, I hope that if a developer considers a feature "moronic" then > they wouldn't include it. You of course can never satisfy everyone, so, > IMHO, best not clutter an application with ill-advised features. I'm working from past experience. I once released an app on mac that had nothing what-so-ever to do with movie editing (mpg,avi,quicktime etc) and because people could not use the app to string bunches of clips together I got flamed. Tons of support email, bad reviews and more than a few I WANT MY MONEY! Never mind the fact that after the first complaint I changed all the listing information and my own site so the first line of the description specifically said it could not string movie clips together. Thus within a few weeks, I released an update with the completely moronic feature (in this app) of being able to string clips together. Anyway people loved it. I have never used the feature for anything outside of testing. I think moronic is too strong of a word perhaps. But this is a touch platform, and it really has significant limits to pixel perfect editing. There are things it does that, I personally find I dunno... too ambitious for a touch platform. At least, in the case of a girl with medium length fingernails(me). Not sure if guys, and gals that trim their nails, will find these things easier than I do. Those that use a stylus will probably really like all the features. I know my stylus changes the playing field significantly. Still the freehand... Honestly even with a stylus, it's only there because I just know if I pull it i'll get slammed with "It's useless because I can't draw!" And those are always the words "It's useless because..." I'd rather risk loosing a star on an otherwise good review for having the feature than only get 1 star for not having it. :\ I know... I'm weighing asterisks at this point... All that said though. If you have twenty minutes - half an hour (maybe a little more on iphone), you can create some absolutely stunning documents with the tools provided. Seriously. I was shocked at the results I was getting because I have such poor graphic design skills. > >> Anyway all I did when I started working in xcode 4.2 was set the >> base sdk to 5.0. I never changed the deployment target away from >> actually, 3.2. Later I implemented ARC but only changed the >> deployment target to 4.2. And this project was originally poorly >> implemented in that there were 2 separate projects, 1 for iPad, 1 for >> iPhone/iPod. So I brought all of the code under one roof and used a >> simple ISIPAD definition (a macro for the interfaceidiom check) to >> figure out what should do what. not that that matters. Anyway. In > > OK, this is what I was getting at in my previous message. > > Let me make sure that I understand correctly. You started out with a > *single UI idiom* (i.e. iPad or iPhone, but not both) project, then > manually created a *universal* app (i.e. one for both iPhone and iPad) > by merging code together? That is to say you NEITHER started a new > Xcode project of the "universal" type NOR ran the "upgrade to iPad" tool > in Xcode? > > If this interpretation is correct, then my previous point remains: you > may have skipped over some important project settings that the build > system is expecting to be configured but aren't (or are configured > improperly). You have it right. And you were right I misconfigured the build settings when I moved to XCode 4.2. (More accurately, did not do anything to them at all.) I know... It would have been much better to convert, or make a new project. I didn't. fortunately the challenges did not effect the performance of the app only getting it to actually be an app. > >> xcode 4.1 the arch had been armv6/armv7 and I never really bothered >> to look at it again after installing the final xcode 4.2. I built and >> ran.. according to the bundle version script's last incrementation at >> release 2673 times over a 5 month period. Installed at least a dozen >> or more adhoc builds via itunes to check some built for release >>
Re: 2 itunesconnect questions
While on this subject I just got the dreaded: Your app will now spend the next 6-12 months in review round file hell before being rejected without further review: "We are currently reviewing an app that you submitted for inclusion on the App Store, and want to let you know that the review process will require additional time" email. Being that there is an iPad specific version that is only being kept up for existing customers and now a universal, iPhone/iPad version which I'm directing new iPad users too, I'm going to end up with both apps getting shot down aren't I? Would I be better to reject both versions, then resubmit the universal one by itself and later the iPad specific with a novel in the reviewer comments about why it's being submitted?___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Preventing Doc based apps from creating docs
I've made a document based application. However whenever I switch to it through the doc a new document is created even though I'm already working on one... I cannot seem to find a way to prevent that from happening. I do not want it to create a new document unless the user requests it. What settings am I missing?___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
iOS Game developer help needed
I'm wondering if some one that's used cocos2d before can answer some sprite sheet questions. I attempted to use a sprite sheet for game buttons but every button has a touchable area equal to the size of the whole sheet___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Serious iPhone 4s & iCloud issue
I have had iCloud working in my app for a very long time. Today I bought a 4s and after getting everything updated, reprovisioned, built and installed my app, the one I've poured hours of blood sweat and tears in to over icloud, cannot access anything stored on icloud. I cannot seem to figure out why. But if I attempt to get a listing of the folders in the storage they are all empty. If I create a document it supposidly goes in to icloud but is inaccessible on any other device. and if I delete the app, no matter how long I wait, it tells me there are pending document updates. Does any one have any ideas on this? April.___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Gamekit - Scores not showing in sandbox
I have an iOS game I'm working on. It has leader boards and while I can get the information progamatically and it is correct, when I display the built in leader board view no scores are visible in the interface. If I back out of the board's view to see the list of boards it shows a ranking and # of players (1) but again if I select a board I know has scores, I do not show up at all. It just says no scores. I'm not really sure I'm 100% on gamekit this way anyway since games are not my thing. But isn't it supposed to show my score in the #1 slot under all players? April.___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
iCloud On OSX - Cannot save changes
On iOS iCloud is easy. On OSX I don't know what the problem is. Ok.. First I had a document on my computer. The using the setUbiquidous method I moved it to iCloud. It is on iCloud, and readable. But thats the problem. I have read only access to it from the Mac App. When I open the document I use : self.document = [[NTPDocument alloc]initWithContentsOfURL:iCloudURL ofType:@"MyDataType" error:&err]; NTPDocument is my subclass of NSDocument. and only implements the dataOfType and readFromData. It also returns YES for autosaves in place. And that's hitch #1. When It attempts to autosave I get an error window in the app that it could not auto save the document because I do not have permission. When I try the saveToURL:ofType:forSaveOperation:completionHandler: I get an "Unimplemented core routine" error (code -4) I have absolutely no clue what this means and cannot for the life of me find the information in the documentation on how to open the file for read/write access. I cannot find a flag or entitlement anywhere that I am missing for allowing me to write to the icloud document... I have attempted to just use [self.document saveDocument:nil] out of desperation but nothing saves, and no error. The main thing being that no matter what way I try to save, my document is never asked to encode the document data. I'm at a loss... Is there possibly an example of working code? Or some part of the documentation that I've not found? I foolishly thought this would be a simple matter of porting my iOS code... If some one has gotten iCloud working for them could you please help? April. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: iCloud On OSX - Cannot save changes
Thanks a lot for the reply. When it is not using iCloud everything works like a dream. It all functions exactly as expected. I only get the permission error with autosave and iCloud. I have reached a point where if I use writeSafely: etc... it will save to iCloud, but I cannot use autosave, I have to set up a timer to fire every x seconds and save if there are changes. April. On Jan 30, 2012, at 11:41 PM, Michael Swan wrote: > April, > You should try saving a non-iCloud document and see if you still have issues. > If so try going through a couple of Apple's basic Mac OS X tutorials to see > if they fill in the holes for you. If you are working with Core Data you can > check out some tutorials I've written for a document based Care Data app at > http://www.theMikeSwan.com/blog. I plan to do an iCloud tutorial as soon as I > have the time. I also have some basic classes for iCloud on GitHub that are > in TMSSupportClasses. There is a bug in 10.7.2 where if you have the same > document open on more than one machine and save changes to it on one of the > machines that others will lose the ability to save to the file until you > close it and re-open it on the machine you want to save from. > Also, if you have iCloud problems that are generating log messages (they may > be hiding in Console.app) about your app doing something that isn't allowed > switch to Finder and navigate to ~/Library/Containers and delete the folder > with your app bundle ID. Some times the container gets messed up and needs to > be re-done. > > Good luck, > Mike Swan > ETCP Certified Entertainment Electrician > http://www.theMikeSwan.com > > > > On 30 Jan, 2012, at 11:15 AM, cocoa-dev-requ...@lists.apple.com wrote: > >> Message: 9 >> Date: Sun, 29 Jan 2012 23:26:41 -0700 >> From: April >> To: list-cocoa-dev >> Subject: iCloud On OSX - Cannot save changes >> Message-ID: >> Content-Type: text/plain; charset=us-ascii >> >> On iOS iCloud is easy. >> On OSX I don't know what the problem is. >> >> Ok.. First I had a document on my computer. The using the setUbiquidous >> method I moved it to iCloud. >> It is on iCloud, and readable. But thats the problem. I have read only >> access to it from the Mac App. >> >> When I open the document I use : >> >> self.document = [[NTPDocument alloc]initWithContentsOfURL:iCloudURL >> ofType:@"MyDataType" error:&err]; >> >> NTPDocument is my subclass of NSDocument. and only implements the dataOfType >> and readFromData. It also returns YES for autosaves in place. >> >> And that's hitch #1. >> >> When It attempts to autosave I get an error window in the app that it could >> not auto save the document because I do not have permission. >> >> When I try the saveToURL:ofType:forSaveOperation:completionHandler: I get >> an "Unimplemented core routine" error (code -4) I have absolutely no clue >> what this means and cannot for the life of me find the information in the >> documentation on how to open the file for read/write access. I cannot find a >> flag or entitlement anywhere that I am missing for allowing me to write to >> the icloud document... >> >> I have attempted to just use [self.document saveDocument:nil] out of >> desperation but nothing saves, and no error. >> >> The main thing being that no matter what way I try to save, my document is >> never asked to encode the document data. >> >> I'm at a loss... Is there possibly an example of working code? Or some part >> of the documentation that I've not found? I foolishly thought this would be >> a simple matter of porting my iOS code... >> >> If some one has gotten iCloud working for them could you please help? >> >> April. > ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: iCloud On OSX - Cannot save changes
Ok that's the problem right there I know for sure. The filecoordinator methods. No they are not wrapped. And nothing else is overridden in my NSDocument subclass. I read about needing to use the NSFileCoordinator but could not find information on how, where, what exactly needed to be done... Just the half paragraph, you need this too stuff in the documentation that more or less tell you absolutely nothing you didn't already know. I honestly want this to be done by the book, but I'm having the worst time finding the book to do it by. April. On Jan 31, 2012, at 8:21 AM, April wrote: > Thanks a lot for the reply. > When it is not using iCloud everything works like a dream. It all functions > exactly as expected. I only get the permission error with autosave and > iCloud. I have reached a point where if I use writeSafely: etc... it will > save to iCloud, but I cannot use autosave, I have to set up a timer to fire > every x seconds and save if there are changes. > > > April. > > On Jan 30, 2012, at 11:41 PM, Michael Swan wrote: > >> April, >> You should try saving a non-iCloud document and see if you still have >> issues. If so try going through a couple of Apple's basic Mac OS X tutorials >> to see if they fill in the holes for you. If you are working with Core Data >> you can check out some tutorials I've written for a document based Care Data >> app at http://www.theMikeSwan.com/blog. I plan to do an iCloud tutorial as >> soon as I have the time. I also have some basic classes for iCloud on GitHub >> that are in TMSSupportClasses. There is a bug in 10.7.2 where if you have >> the same document open on more than one machine and save changes to it on >> one of the machines that others will lose the ability to save to the file >> until you close it and re-open it on the machine you want to save from. >> Also, if you have iCloud problems that are generating log messages (they may >> be hiding in Console.app) about your app doing something that isn't allowed >> switch to Finder and navigate to ~/Library/Containers and delete the folder >> with your app bundle ID. Some times the container gets messed up and needs >> to be re-done. >> >> Good luck, >> Mike Swan >> ETCP Certified Entertainment Electrician >> http://www.theMikeSwan.com >> >> >> >> On 30 Jan, 2012, at 11:15 AM, cocoa-dev-requ...@lists.apple.com wrote: >> >>> Message: 9 >>> Date: Sun, 29 Jan 2012 23:26:41 -0700 >>> From: April >>> To: list-cocoa-dev >>> Subject: iCloud On OSX - Cannot save changes >>> Message-ID: >>> Content-Type: text/plain; charset=us-ascii >>> >>> On iOS iCloud is easy. >>> On OSX I don't know what the problem is. >>> >>> Ok.. First I had a document on my computer. The using the setUbiquidous >>> method I moved it to iCloud. >>> It is on iCloud, and readable. But thats the problem. I have read only >>> access to it from the Mac App. >>> >>> When I open the document I use : >>> >>> self.document = [[NTPDocument alloc]initWithContentsOfURL:iCloudURL >>> ofType:@"MyDataType" error:&err]; >>> >>> NTPDocument is my subclass of NSDocument. and only implements the >>> dataOfType and readFromData. It also returns YES for autosaves in place. >>> >>> And that's hitch #1. >>> >>> When It attempts to autosave I get an error window in the app that it could >>> not auto save the document because I do not have permission. >>> >>> When I try the saveToURL:ofType:forSaveOperation:completionHandler: I get >>> an "Unimplemented core routine" error (code -4) I have absolutely no clue >>> what this means and cannot for the life of me find the information in the >>> documentation on how to open the file for read/write access. I cannot find >>> a flag or entitlement anywhere that I am missing for allowing me to write >>> to the icloud document... >>> >>> I have attempted to just use [self.document saveDocument:nil] out of >>> desperation but nothing saves, and no error. >>> >>> The main thing being that no matter what way I try to save, my document is >>> never asked to encode the document data. >>> >>> I'm at a loss... Is there possibly an example of working code? Or some part >>> of the documentation that I've not found? I foolishly thought this would be >>> a simple matter of porting my iOS code... >>> >>>
Re: iCloud On OSX - Cannot save changes (Resolved?)
Ok a little info I "discovered" the WWDC video on NSFileCoordinators etc... I watched it front to back Took notes It helped a little. What helped more than anything though was the suggestion I check the console app. I found a message there about a sandbox block on my app. I picked bit by bit through the message. The chain of events was fairly obvious. I used the info I learned in the video to overcome the problem. Autosave with iCloud now works, I assume, as intended. I over rode the saveToURL: method that failed, and used the filecoordinator to fix it all. April. On Jan 31, 2012, at 10:57 PM, April wrote: > Ok that's the problem right there I know for sure. The filecoordinator > methods. No they are not wrapped. And nothing else is overridden in my > NSDocument subclass. > I read about needing to use the NSFileCoordinator but could not find > information on how, where, what exactly needed to be done... Just the half > paragraph, you need this too stuff in the documentation that more or less > tell you absolutely nothing you didn't already know. I honestly want this to > be done by the book, but I'm having the worst time finding the book to do it > by. > > April. > > On Jan 31, 2012, at 8:21 AM, April wrote: > >> Thanks a lot for the reply. >> When it is not using iCloud everything works like a dream. It all functions >> exactly as expected. I only get the permission error with autosave and >> iCloud. I have reached a point where if I use writeSafely: etc... it will >> save to iCloud, but I cannot use autosave, I have to set up a timer to fire >> every x seconds and save if there are changes. >> >> >> April. >> >> On Jan 30, 2012, at 11:41 PM, Michael Swan wrote: >> >>> April, >>> You should try saving a non-iCloud document and see if you still have >>> issues. If so try going through a couple of Apple's basic Mac OS X >>> tutorials to see if they fill in the holes for you. If you are working with >>> Core Data you can check out some tutorials I've written for a document >>> based Care Data app at http://www.theMikeSwan.com/blog. I plan to do an >>> iCloud tutorial as soon as I have the time. I also have some basic classes >>> for iCloud on GitHub that are in TMSSupportClasses. There is a bug in >>> 10.7.2 where if you have the same document open on more than one machine >>> and save changes to it on one of the machines that others will lose the >>> ability to save to the file until you close it and re-open it on the >>> machine you want to save from. >>> Also, if you have iCloud problems that are generating log messages (they >>> may be hiding in Console.app) about your app doing something that isn't >>> allowed switch to Finder and navigate to ~/Library/Containers and delete >>> the folder with your app bundle ID. Some times the container gets messed up >>> and needs to be re-done. >>> >>> Good luck, >>> Mike Swan >>> ETCP Certified Entertainment Electrician >>> http://www.theMikeSwan.com >>> >>> >>> >>> On 30 Jan, 2012, at 11:15 AM, cocoa-dev-requ...@lists.apple.com wrote: >>> >>>> Message: 9 >>>> Date: Sun, 29 Jan 2012 23:26:41 -0700 >>>> From: April >>>> To: list-cocoa-dev >>>> Subject: iCloud On OSX - Cannot save changes >>>> Message-ID: >>>> Content-Type: text/plain; charset=us-ascii >>>> >>>> On iOS iCloud is easy. >>>> On OSX I don't know what the problem is. >>>> >>>> Ok.. First I had a document on my computer. The using the setUbiquidous >>>> method I moved it to iCloud. >>>> It is on iCloud, and readable. But thats the problem. I have read only >>>> access to it from the Mac App. >>>> >>>> When I open the document I use : >>>> >>>> self.document = [[NTPDocument alloc]initWithContentsOfURL:iCloudURL >>>> ofType:@"MyDataType" error:&err]; >>>> >>>> NTPDocument is my subclass of NSDocument. and only implements the >>>> dataOfType and readFromData. It also returns YES for autosaves in place. >>>> >>>> And that's hitch #1. >>>> >>>> When It attempts to autosave I get an error window in the app that it >>>> could not auto save the document because I do not have permission. >>>> >>>> When I try the saveToURL:ofType:forSaveOperation:completionHandler: I >>>&
