4.3

No. https://developer.apple.com/app-store/review/guidelines/ 4.3 Spam

Assuming you are a registered MFI developer then the spec for the QR code is documented in the HomeKit Accessory Protocol Specification - in version R15 of that spec it is in section 4.3. You can download the spec from the MFI website when you log in on your account.

Hi Jinkal, I come across your question in other post in relation to the “4.3 spam - your app primarily features astrology, horoscopes, palm reading, fortune telling or zodiac reports. as such, it duplicates the content and functionality of many other similar apps currently available on the App Store” just wondering if your app has successfully surpass this issue in the end? I’m coming across the same issue. Any lights shed would be appreciated.

I have an iMac 2014 5k with 32 GB Ram, The system can't manage the memory. most of the time I have 4.3% to 12% free memory. And the speed is so low for simple tasks.

There are a number of app genres that the App Store reviewers decided to be too saturated. Among those are astrology, horoscope, palm-reading, and similar tell-your-future-from-your-biometric apps. If your app is one of those, you can't publish it on the App Stores. You could try publishing it as a Developer ID macOS application – use Catalyst if it's an iOS app. However there are other causes of Guideline 4.3 Spam rejection: Publishing similar apps that differs only in content. Publishing white-label apps under your own Developer Account. A competitor's app looks similar to yours. Search the web for How to Pass App Store Review: Guideline 4.3 Spam to find out how to diagnose the problem further as well as some potential solutions.

This is an interesting thread, thanks for the orig post. I was under the impression that Metal was almost always faster than OpenCL because OpenCL is and old and clunky higher level API, but Metal goes right to the metal as they say. I guess not? I would suggest looking into the global memory access times if you can, e.g. the read-write refs to the device declared arrays. I am unsure of the latest tools for this, but you can try to check into the problem by removing device arrays from the picture and just doing fake calculations. E.g. try to set up some local arrays in thread or threadgroup storage instead of device storage for the arrays xyin, xyout and spherical_params (see https://developer.apple.com/metal/Metal-Shading-Language-Specification.pdf section 4.3) and dont even bother to initialize them. Just let the array dereferences and calculations stay the same in your kernel and let it run on bogus float data in those threadgroup arrays. See if it is faster. It should be a lot faster. If it is fa

Apple rejected many times.What to do ? Please help me. 4. 3 Design: Spam Guideline 4.3 - Design - Spam Your app primarily features astrology, horoscopes, palm reading, fortune telling or zodiac reports. As such, it duplicates the content and functionality of many other similar apps currently available on the App Store. While these app features may be useful, informative or entertaining, we simply have enough of these types of apps on the App Store, and they are considered a form of spam. Next Steps We encourage you to review your app concept and incorporate different content and features that are in compliance with the App Store Review Guidelines.

The established technique is to examine the receipt of the app. It will have a field in it entitled original_application_version. That will indicate the 'Build' number (unfortunately not the Version number!!!) of the app that the user originally purchased. In your 'new' free app you use a different Build number - like 4.1 then 4.2 then 4.3. You use that Build number to separate the paid purchases from the free purchases.(iOS - Build number; for Mac Apps it's the version number)https://developer.apple.com/library/archive/releasenotes/General/ValidateAppStoreReceipt/Chapters/ReceiptFields.htmlhttps://forums.developer.apple.com/message/11915#11915https://forums.developer.apple.com/message/185419#185419