I decided to do some cleanup and remove some of them, starting with Kongregate.
Now that the original Unity webplayer is no longer supported by modern browsers, I have non-functioning games on various game portals. Learn Unity 4 No More was originally published in Technicat Apps on Medium, where people are continuing the conversation by highlighting and responding to this story. At least until I work on a new edition of the book (don’t hold your breath). So I’m breaking my “If it ain’t broke, don’t unpublish it” rule, and the Learn Unity app is no more. And I was getting tired of app reviews like “It’s just the sample project from a book” and “It’s just like fortnite!” (I don’t know if I prefer stating the obvious or stating the sarcastic). It made maybe a few bucks in Unity Ads revenue, but it’s never going to pay the mortgage. The book(s) are obsolete, so I’m not really trying to get anyone to buy the book, anymore.
#HYPERBOWL UNITY EDITS CODE#
I renamed the app Learn Unity 4 after a second edition of the book came out, Learn Unity 2017 for iOS Game Development, because I don’t know what changed in that update, and then I rewrote the code in C# because Unity no longer supports Unityscript a.k.a Javascript, and then as I was adding keyboard controls so I could deploy it as a webplayer on itch.io, it occurred to me, why am I still updating this app? The latest casualty is my Learn Unity app that was the published working project sample from my book Learn Unity 4 for iOS Game Development. So, I never achieved anything near a hundred apps and, on the contrary, have been going the opposite direction. Anything that hasn’t been updated in six months looks like abandonware. They have to be rebuilt on a regular basis to accommodate new app store policies and new platforms, and users expect improvements and fixes.
#HYPERBOWL UNITY EDITS PRO#
When I started putting apps on the App Store and Google Play, I thought I should be able to publish a hundred apps, reasoning I wanted to get my money’s worth out of the developer fees and tools (Unity Pro cost a significant amount back then), and even if I just made a little bit from each app, it would add up.īut the thing is, apps require support. NSPhotoLibraryAddUsageDescription was originally published in Technicat Apps on Medium, where people are continuing the conversation by highlighting and responding to this story. Really, anyone who’s editing the ist file does not need to be shielded from the actual key names - Apple, you’re not doing anyone any favors here. In any case, the next step is to figure out which English version of the key should be selected. It seems to me that it would be a better user experience to, say, not crash, and do nothing. I thought this type of thing would result in an app review rejection, but it will just crash when the app tries to bring up the permissions dialog, and not only does it crash, it does it deliberately, as indicated by the log.
I know this now because a user of my Talk Dim Sum app reported the app is crashing when he tries to save a dim sum photo to his photo library using the share ( UIActivityViewController) popup.
I guess I’m late to the party, but, beginning with iOS 11, the NSPhotoLibraryAddUsageDescription key and accompanying text must be included in the ist file if the app tries to add photos to the photo library.
0 kommentar(er)
