Great - thanks for the update!

Terrible "service" for subscription paying customers. We're being totally ignored on this issue. I've wasted MONTHS of subscription waiting for this fix and its still not addressed, not even a comment, and it's a show-stopper for me.

What's the point in new releases of C3 for minutia "bug fixes" when one of the main functionality areas (exporting with WORKING ads) has been broken for months?

Scirra constantly compares its subscription model to companies such as Unity, can you imagine this level of "service" at Unity? They'd be out of business.

Scirra appears to want the constant revenue of the subscription model, but without any of responsibility to maintain a usable tool that is compliant with the App Store or Google Play. You cant have it both ways Scirra - you have to maintain the features advertised.

Scirra, PLEASE fix this issue ASAP!

Can't tell you about the inner workings of the company as i not partake in it. Maybe because there are like 30 different threads on this forum about 30 different things to implement all with the same urgency?

And therein lies the issue as to why devs and businesses cannot rely on C3 as a serious tool. Imagine a company waiting around for months/weeks for a critical feature to be implemented? Paying staff and rent and hearing nothing from Scirra regarding a fix. No feedback whatsoever.

Apps now require the feature I commented on on both Google Play and the Apple App store. It's critical as an app is in policy violation without the feature. Yet here we are months later and nothing from Scirra regarding implementation in iOS.....

I think a customer-faith issue for Scirra is how the threads are locked if people criticize the subscription based model. That's not good; let the thread lose interest naturally. When you silence people's opinion it looks suspicious to the paying customer. Alternatively, to be fair, lock any thread that sings the praises of C3 - as all that has been said before too.

I think the original thread mentioned here had good feedback on both sides and there was no reason to lock it.

Also, Scirra supporters keep harping back to the subscription model allowing for faster updates and implementation of new features. If so, could you please explain why we have been waiting MONTHS for implementation of the General Data Protection Regulation (GDPR) functionality so that we can list our apps on the Apple market? Our subscription is ticking away as we wait, yet threads on the issue remain with no comment from Scirra for months, even when specifically asked in the thread.

It seems the mods/owners are soon to lock/comment on threads that are deemed "anti-Scirra", but less enthusiastic when paying customers ask for status on features that are show-stoppers for many.

Just my 2c.

Mod locking thread in 3...2...1.... :)

...another 3 weeks have gone by and still no official feedback on a fix for iOS?

This is costing me subscription $ guys :(

Hello all,

Does anyone know if its possible to perform the following?

1) Tap and drag a sprite.

2) A cloned sprite is created on drop (leaving the original in place).

3) User taps cloned sprite to rotate it 10 degrees while the original non-cloned sprite does not rotate.

4) User can create more cloned sprites that rotate individually from each other.

I can create a cloned sprite and rotate it, but the cloned and original sprites both rotate.

Thanks!

I get this error too. Exporting as signed APK (Android) with C3 project file on Google Drive.

Try this:

https://stackoverflow.com/questions/453 ... le_rich_qa

HTH.

When you encounter an issue like this that is supposed to be a bug, do visit the bug database and see if the bug was already reported. If it was, consider adding a comment to it.

If it wasn't, consider posting a new report.

And to provide some actual true informations, each dev at the HQ works on several features.

As far as I'm aware, the runtime has been Ashley's work, and Nepeo deals with the build service.

But how about some pre-emptive work so that customers don't spend repetitive time filing the same bug over and over again? Perhaps devs should NOT be working on several features, but concentrate on the cash cow of the C3 browser-based option. Anything else is gravy.