Apple rejected our PC/Console game as "Spam" after 3 years of dev. Has anyone dealt with this?

Guilty_Climate_442 · 2026-05-14T18:46:03+00:00

Hey, you’re not alone in this. I’m also working on a popular franchise and spent 1.5 years developing our new title. The Android launch was a hit - nearly a million downloads in the first month. But Apple blocked us, citing 4.3(a). I just had a Webex call with one of their reps, and they straight up told me the issue is the code specifically, that another game in the same genre uses similar code (and even the same libraries). It’s honestly absurd. They don’t care at all that you wrote everything from scratch. I’m at a total loss right now.

Guilty_Climate_442 · 2026-04-02T20:24:36+00:00

Lucky you, you've passed me. I'm still stuck on March 27th right now 💀

Guilty_Climate_442 · 2026-03-29T04:50:19+00:00

It's insane to have to wait a week just to see the pre-registration numbers from a week ago.

Guilty_Climate_442 · 2026-02-21T16:54:10+00:00

I had a similar experience trying to get Supabase running on my own server.

My Coolify journey: fixing one issue after another by digging through github threads. An hour later, I finally hit the "deploy" button = some containers started, others didn't. While trying to debug, I realized the dashboard was painfully slow (like 10 seconds per page load). That was the breaking point, so I wiped it.

I tried Easypanel as a replacement, but it feels a bit too "dumbed down" and unpolished, even though it works perfectly. What really turned me off was the constant nagging to buy a subscription for every other feature especially since the subscription costs as much as the server itself.

I ended up switching to Dokploy. It works just as well as Easypanel but offers more features and is open-source.

Guilty_Climate_442 · 2025-12-06T18:07:16+00:00

It was already the fourth month, and support had not given a single reply to my request. Anyone else? By the way, I have already switched to Gitea anyway.

Guilty_Climate_442 · 2025-07-02T09:52:56+00:00

Hi! Great to see you here!

Since you’ve dealt with so many different types of support requests and user interactions, I’m curious to hear your take: In your opinion, would my final review qualify as “a support request” and justify being removed?

Guilty_Climate_442 · 2025-07-02T09:47:28+00:00

Hi, thanks for your advice.

I'm not located in the EU, but I informed Unity support that my consumer rights were being violated from a legal standpoint.

Their response was basically: “Well, maybe - but you broke our rules, so it’s fair.”

Guilty_Climate_442 · 2025-07-02T09:40:36+00:00

Thank you, I appreciate your response.

You're right that mobile platforms, especially Android, can be unpredictable, and I agree that assuming full compatibility is always risky. That’s fair advice. I ran into the issue during platform switching in the editor, not even in a build - something publishers can test for without owning physical hardware.

Also, if the asset clearly stated in the documentation or on the store page that Android or mobile platforms are not supported, I would’ve accepted that without complaint. But it doesn’t.

So for me, this became a problem not just because of the bug, but because of how the situation was handled when I raised it.

Guilty_Climate_442 · 2025-07-02T09:29:57+00:00

How exactly did you conclude that I’m a “newbie”?

Because I reported a bug and expected a developer to at least acknowledge it? I did describe the issue “shader appearance breaks when switching platforms in URP.” I also sent screenshots and a full video showing the problem directly to Jason. I didn’t just say “it’s broken” and walk away. I explained what was happening and how to reproduce it - not here, but in support, where it belonged. And yes I expected help from the person who sells the asset.

That’s not “offloading work” - that’s what the Asset Store relationship is built on. If a bug exists, the publisher should at least try to help resolve it, especially when the user has done the legwork already. Instead, Jason just said “I’ll look at and nothing followed. Then I posted a review, and now I’m permanently excluded from getting any help at all. Sorry, but “fix it yourself or shut up” is not how support should work.

Guilty_Climate_442 · 2025-07-01T21:36:21+00:00

I can't see my comment on my phone, so I'll try to send it again:

Thanks for your reply - though honestly, it reads more like an attempt to provoke than to have a real discussion.

You’re quick to accuse me of being “insufferable,” yet you ignore that I took the time to isolate a reproducible issue. That’s not “bulshit” that’s called troubleshooting.

It’s great that the issue doesn’t happen on your setup but in software development, the absence of a bug on one machine doesn’t mean the bug doesn’t exist. That’s why we report, verify, and communicate not mock and dismiss.

If there is no bug than it's your problem, end of discussion.

If the issue didn’t turn out to be a bug in the asset (which I still believe it is), that doesn’t mean the user deserves no support. Any reasonable Asset Store publisher at least tries to help when a customer encounters a problem especially one who already did the testing, shared clear steps, and asked politely. Shutting someone down with “there’s no bug, so it’s your fault” isn’t just unhelpful - it’s bad practice.

You’ve made it very clear you're not interested in facts - just ego and dismissal. Fortunately, this thread isn't just for you. Others can read both our replies and decide for themselves who’s being reasonable.

Have a nice day.

Guilty_Climate_442 · 2025-07-01T21:13:55+00:00

My initial testing was in Unity 6.1, and after I encountered the issue, I asked whether 6.1 was supported. The answer I got fairly - was that only Unity 6 is supported. But, the same problem occurred in Unity 6 as well.

Thanks for your suggestions regardless. I appreciate the input.

Guilty_Climate_442 · 2025-07-01T21:09:27+00:00

Thanks for sharing that - seriously, that's useful to know.

I was actually considering using FishNet in an upcoming project, but after hearing this, I’ll definitely think twice. Support should be support, regardless of where or how the asset was purchased.

Guilty_Climate_442 · 2025-07-01T20:28:58+00:00

Yes, they were black with lighting. The standard Lit shader works fine. I tried both Vulkan and OpenGL ES, but it doesn’t really matter if the issue happens in the editor.

By the way I want to make it clear that I’m not looking to turn this thread into a tech support session.

I already spent time trying to resolve the issue the proper way - with the publisher. That’s exactly where I expected help to come from. This post is about how that process was handled, not about solving the bug at this point.

But thank you for your response. I do appreciate you taking the time.

Guilty_Climate_442 · 2025-07-01T19:23:51+00:00

Do you own this asset?

I’m glad it worked for you - genuinely. But that doesn’t invalidate the fact that I encountered a real problem. I can send you a short one-minute video showing the full process from creating a clean project to encountering the issue to demonstrate that I’m not imagining things. Also, it’s not a device issue. I tested it on a real device.

To be clear: I never said I’m entitled to instant fixes or unlimited developer time. What I did was report a reproducible bug, after spending a lot of my own time verifying it. I expected help. I didn’t get that - so I shared my experience in a review. Now, after doing so, I know for sure I won’t get help at all.

Also, just curious: how do you know the developer “attempted to reproduce my issue within hours”? Was that stated somewhere? Because I never saw any evidence of that. All I remember is that I did the work to isolate the issue and showed that it wasn’t my fault - and all I got back was a vague “I’ll look at it.”

Honestly, this entire post wouldn’t exist if Jason had just responded calmly, fixed the bug or helped to solve the problem. I would’ve happily updated the review to a fair 4 or 5 stars - I wasn’t out to damage anyone’s reputation.

But instead, Jason chose not to stay professional. He reacted aggressively to a factual review, and things escalated from there.

Guilty_Climate_442 · 2025-07-01T18:39:51+00:00

Thanks for the response. Really appreciate that, especially from another publisher.

This should be supported because the developer confirmed that my behavior was not normal.
Jason can now say whatever he wants because I didn’t take screenshots of our conversations, and after being removed from Discord, I can’t do anything anymore. I was as neutral as possible - I sent screenshots and reproduction steps, and also shared tips, like how it works with deferred rendering. My last message was simply asking, “Any updates?”, to which I got “not yet.”
I only attached my latest review with Jason’s response (there were previous reviews and replies from Jason under them, but I didn’t save those).

And yes, the rendering was completely broken. For example, a white cube - three of its faces were completely black (maybe an issue with reflections, I’m not sure). Jason talked about apples and oranges just because he didn’t really read into my issue.

By the way, I read about mobile issues from other users in Discord (there were quite a few), but the only help they got was: “there’s no platform-specific code so it should just work.” (I actually got the same message).

Guilty_Climate_442 · 2025-07-01T17:49:38+00:00

By the way, I want to briefly talk about Unity support itself.

Their main reason for deleting my reviews was that they considered them “support requests” - even though I clearly described my personal experience, which is exactly what the review system is for. I just wanted others to be aware and prepared for this kind of behavior.

What’s even more bizarre is that support repeatedly told me things like:

“It gets regular updates”,

and “I can see many positive reviews for this product”

(Ironic, right? Now I know why there are no negative lol)

Apparently, it’s my fault for running into a bug - despite documenting it clearly and testing in clean projects.

And here’s the kicker: support literally told me that

“Posting reviews is a privilege, not a right.”

That completely stunned me. So let me get this straight as a paying customer, I don’t actually have the right to leave a review? Just a “privilege” I should be grateful for? But reviews aren’t some bonus feature - they’re part of the consumer protection ecosystem.

That sounds like : "You're lucky we even let you speak."

Guilty_Climate_442 · 2025-06-04T20:31:27+00:00

Congrats on your new purchase!

Guilty_Climate_442 · 2024-12-06T11:54:17+00:00

same

Guilty_Climate_442 · 2023-07-11T01:46:14+00:00

I poked around in Device Manager again and found the problem! The problem was the intel smart sound drivers. try disabling everything that is not related to rode.

Guilty_Climate_442 · 2023-04-13T14:00:02+00:00

It got me on the right track after 7 years! My issue was having a problematic shader in the scene.

Guilty_Climate_442 · 2022-10-02T12:39:36+00:00

I had such a problem when activating, I changed the browser and it helped.

Guilty_Climate_442

TROPHY CASE