I have read the disconnected documentation for adding a simple complication that ONLY launches my app using the asset images I've created in various sizes for various families along with the ComplicationController code, but the complications never appear (with no errors). I would like to support Watch Series 1 with OS 4.3 on up. There never seems to be one place where this simple, default function is documented. What are the steps and code required to just launch a Watch app from a complication?
4.3
402 results found
Post
Replies
Boosts
Views
Activity
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.
According to Apple's new policy ( https://developer.apple.com/news/?id=84w3e5bm ) - bug fixes will no longer be delayed over guideline violations except for those related to legal issues. You’ll instead be able to address guideline violations in your next submission.. In 2019 updates to my apps were rejected due to apple Guidelines (note - not safety, not legal - guidelines) violation 4.3 - smap (I have only few of them and they are NOT reskins - they do share similar functionality, though not the same, and different graphics - they are similar only in a way any match 3 is similar to each other). A week ago I wanted to publish and update (SDK update and bugfixed, not gameplay or etc) again, and was still rejected - though obviously it should be allowed. Correct me if I am wrong or misunderstood the sentence from the top of my post. Otherwise whom do I contact to change my reviewer for the one that follows rules? Thank you
Hi, I've built my own Collaboration/Messenger App based on Rocket.Chat from the open source, bound to my server and necessary to receive push notifications from my server. My app was refused today with: Guideline 4.3 - Design We noticed that your app provides the same feature set as other apps submitted to the App Store; it simply varies in content or language, which is considered a form of spam. The next submission of this app may require a longer review time, and this app will not be eligible for an expedited review until this issue is resolved. Guideline 4.2 - Design - Minimum Functionality We found that the usefulness of your app is limited because it seems to be intended for a small, or niche, set of users. I'm pretty puzzled. Regarding 4.2, how should I deploy an app to potential 250 users of my sports club if not via the AppStore. This is not a company where BusinessManager etc. can be used, I have no control over any devices. But finally 4.3 ... what I read my understanding of Spam i
my app was creating problem with deseign spam but somehow i managed to make it work and get accepted by apple store but now while updating it, it still showing same issue 4.3 spam I am totally ****** off and losing hope for my business, can anybody have any solution
My app rejected in from apple side. How can I solve this issue? Guideline 3.2 - Business During our review, we found that this app was designed for a specific business or organization, including its partners, clients or employees, and not for general distribution on the App Store. Business apps available on the App Store are meant for use by a wide variety of external customers around the world. As this app is not intended for general distribution, it cannot be made available on the App Store. We encourage you to review the other ways to distribute your business app and choose one that better meets your business needs. If you revise your app concept and features to provide substantial value to a wide variety of external customers around the world, we recommend that you also review our App Store Review Guidelines, including, among others, guidelines 2.5.4 - Background Location, 3.2.2 - Unacceptable Business Models, 4.0 - Design, 4.2 - Minimum Functionality, and 4.3 - Spam, prior to resubmitting the ap
Hi, we submitted our app for review after 1 year of development, and 4 months waiting to finally make payment and enable developer account. After review, app was rejected for 4.3 reason design spam as there are already lots of dating apps in the store reason. We have a unique audience and features (of course also common features like other dating as cannot be avoided chat, some like function etc), and a lof of users were looking forward to our ios version, they are still using the web and ask us every day when they can use ios app. App got rejected and what is unfair is that we can mention at least 5 apps that are total trash in terms of features that do exist in app store same category and are our rivals published without any problem. We submitted after 2 weeks a totally new concept for the app, new menus, animations etc to make it more unique so is not anymore under design spam. Now it was rejected again for same reason and we are out of ideas what to change for the next submission. Our designers a
Dating app removed for 4.3 design spam. What would be the easiest way to get approved again?
Hi Team, I am getting the below error when I build the app. Please someone guide me in resolving this issue? I have already tried these solutions. 1) Enable bitcode --> No Undefined symbols for architecture x8664: boost::redetail106300::perlmatcher<char const*, std::_1::allocator, boost::regextraits<char, boost::cppregextraits >::find(), referenced from: bool boost::regexsearch<char const*, std::1::allocator, char, boost::regextraits<char, boost::cppregextraits >(char const*, char const*, boost::matchresults<char const*, std::1::allocator >&, boost::basicregex<char, boost::regextraits > const&, boost::regexconstants::matchflags, char const*) in libFlipper-Folly.a(Uri.o) folly::detail::crc32ccombinehw(unsigned int, unsigned int, unsigned long), referenced from:... yarpl::credits::add(long long, long long), referenced from:... yarpl::credits::consume(long long&, long long), referenced from:... folly::init(int*, char***, bool), referenced from:... boost::redetail10630
Hi guys, The ultimate carnage 2 is the sequel to the ultimate carnage on the app store. Witch is my own games. The game is totally different, it adds many new game modes, graphics and performance improvements. So I don't understand why it was rejected under 4.3 Design spam guidelines. How can I get my game to be accepted ? Thank you!
Hi, We keep receiving this response from the App Store review: Guideline 4.3 - Design This app duplicates the content and functionality of other apps submitted by you or another developer to the App Store, which is considered a form of spam. Apps that simply duplicate content or functionality create clutter, diminish the overall experience for the end user, and reduce the ability of developers to market their apps. Next Steps Review the Design section of the App Store Review Guidelines. Ensure your app is compliant with all sections of the App Store Review Guidelines and the Terms & Conditions of the Apple Developer Program. Once your app is fully compliant, resubmit your app for review. And those are the main steps to reproduce the issue: Create our app. Submit the app to the App Store. The app got approved. Our business has requested a different bundle ID. Remove our app. Recreate our app with a different bundle ID. Submit the app to the App Store. App got rejected. Several messages, emails hav
Guideline 4.3 - Design This app duplicates the content and functionality of other apps submitted by you or another developer to the App Store, which is considered a form of spam. Apps that simply duplicate content or functionality create clutter, diminish the overall experience for the end user, and reduce the ability of developers to market their apps. The next submission of this app may require a longer review time, and this app will not be eligible for an expedited review until this issue is resolved. Next Steps Review the Design section of the App Store Review Guidelines. Ensure your app is compliant with all sections of the App Store Review Guidelines and the Terms & Conditions of the Apple Developer Program. Once your app is fully compliant, resubmit your app for review. Submitting apps designed to mislead or harm customers or evade the review process may result in the termination of your Apple Developer Program account. Review the Terms & Conditions of the Apple Developer Program to le
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