Skip to main content

Apple App Store Rejection - My Situation

Didn't expect this!

I've been working on a React Native application for a hypnotherapist which as a proof-of-concept was an app with instructions on how to use the hypnotic track. 

The process has been immensely fun jumping straight into creating a React Native application because of one particular module and its functionality.

Not going to digress into the story behind the app - that will be another blog post, we're here for the Apple rejection story.

Initially I thought there may be issues publishing onto the Apple store when I was publishing to Android and it took nearly five days to complete the review. There wasn't any feedback on it but I was glad to see it passed is published on Android.

The Apple process was pretty convoluted to submit the application but it was finally done. Very impressed Apple were able to review the application so quickly! Well done to the Engineers!

This morning I go this message regarding the application:


That's not good!

So, what is this guideline?

You can find the app store guidelines here. We are interested in section 4.2 - Design - Minimum Functionality:


Fair game to Apple, I can see from the face of it why they would reject the application. If this were a song and media player I had created for just one song then rightly they could reject it. The app in question required information to go along with it on how to use it, what to do if something goes wrong, what the track was for, what is anxiety and how we treat it. These things couldn't safely be included in a MP3.

I submitted an appeal to get the application published based on the reasons I've mentioned above and now it is going to be a waiting game to see if Apple agrees or if I now need to now find new functionality to add an improve the application. 

The question will be if the application is rejected, what functionality to add? 

I am lucky in the sense that I am working on this app pro bono or for no charge for the client but if I were billing a client and then had to go back with and explain their application has been rejected and now we need to add more functionality ($$$) to get it on the Apple app store. 

What would you do if you were in that situation? Has this or something similar happened to you?

I'll keep an eye on situation and update keep you all posted on what happens - hopefully it gets approved! 

Now we wait...

Comments

Popular posts from this blog

Adding a space to your iOS App Name

How to add a space to your display name There is a cap of sorts for iOS applications where once your display name exceeds 12 characters, it will strip any spaces in it. There are a lot of posts on StackOverflow about this, however the missed one small detail on how to edit the value. What we need to do is edit info.plist. You can try this in Xcode but it doesn't work, you need to use another text editor - in my case I used Visual Studio Code. Your directory structure may vary, here I am working on a React Native project. Instead of iOS, your root folder may be your project name.  Go to: build > * Your application name * > edit info.plist The value we want to update is " CFBundleDisplayName ".  Where the space(s) are, we need to replace the space here with:      Your CFBundleDisplayName should then look like this: That is all there is to it! Hope this helps you out.

How to enable the lock screen for your Android Emulator

Here's how: When I was testing and app with media controls, I would press the lock button, once to lock the screen and a second to unlock it which would instantly unlock it and take you to the app.  By setting the option for ‘swipe’ when unlocking the screen (pressing the power button the second time) you are now presented with the lock screen and can swipe/drag the screen upwards to go the application Go to Settings --> Security --> Screen Lock Choose 'Swipe' That's all there is to it!

Xcode - ld: library not found for -lDoubleConversion

Here's how you fix this issue Ran into this with the iOS version of my React Native application, the fix is very quick and easy: We need to disable dead code stripping for our release, this is how to do it: Open XCode and press: Cmd + 1 Click on your project in the left panel Click on "Build Settings" In the "Linking" section, under the "Dead Code Stripping" section, change the setting for "Release" from "Yes" to "No"