[quote:1cjy294t]Correct me I'm wrong but you still can't export a ready-to-ship APK file from C3?

I certainly can export an "unsigned APK" directly from C3 ... VERY VERY EASILY, compared with the old Intel XDK method.

Here's the process. Bold texts show the number of clicks:

MENU >

PROJECT >

EXPORT >

ANDROID (CORDOVA) >

NEXT (to skip compression options) >

Select Unsigned release APK & press NEXT >

Wait for the upload, and build >

Press the download link in the pop up

Once you have the UNSIGNED APK ... you'll need to sign and zipalign it. I do this via command line prompt (takes 30 seconds for me). THEN it is ready for upload

That's interesting. Why isn't this functionality clearly documented. If I remember correctly, in C2 I had to juggle a list of XDK projects and pray that XDK never went away - taking my source with it. Thanks for the info - now Im a little more intrigued. Im familiar with Android Studio and signing/zipalign etc.

Have you tried adding ads for AdMob/Amazon yet?

> The main issue with Construct is the problematic exporting to Android/iOS etc, and it seems none of that was addressed. Is C3 just a money grab?

>

Android exporting is BRILLIANT in C3. Super quick and easy!

A minor hiccup in Admobs, but I've got it working flawlessly (including the new reward videos), and Google Services plugin should have been fixed in latest beta.

I upgraded from C2 6 months ago. Well worth the money!

Correct me I'm wrong but you still can't export a ready-to-ship APK file from C3?

I have no doubt there were improvements to processes in C3, but without a robust iOS/Adroid export it's a pain and not worth the hassle.

My reason for asking is that I just removed 10 apps from my Google Play that I previously created with C2. Over the last 18 months, all 10 fell out of favor with Google for issues with the Cordova plugin - part of the C2 export APK creation dance. For the small amount or revenue they generated, going through the export/XDK dance for 10 game updates just wasnt worth it. I deleted them and went back to Android Studio.

So unless C3 can generate an APK from C3 itself, C3 is still just a fun entertainment app to play at being a developer - certainly not worth the 'dev level' price tag.

Hello,

I've been off the scene for a year or so and just finding out about C3 being released. I don't get it. If i monetize some of my apps, C3 costs more than C2, no "deal-breaker" new features, and still all of the hokey, and extremely temperamental, export "to all OS" types procedures.

I have no intention of upgrading to C3 from C2 - why would I ? The main issue with Construct is the problematic exporting to Android/iOS etc, and it seems none of that was addressed. Is C3 just a money grab?

Thanks.

I see. Thanks so much

Anyone.....anyone....

Don't worry, ads still serve in C2 apps after Sept 15th.

Thanks. On what documentation do you base that belief upon?

Hello,

I recently received this email from Google:

"AdMob is committed to providing you the most effective monetization solutions. As we innovate, it’s important that we leverage the latest technologies to bolster our platform. As part of this movement, we are deprecating versions 6.4.1 and lower of the Android Google Mobile Ads SDK on September 15th, 2016.

In order to ensure that your ads continue to serve after September 15th, 2016, please upgrade to Google Mobile Ads SDK 7.0.0 or higher."

Will ads still serve in our C2 apps after Sept 15th?

Thanks all.

Here's the problem: Google Play states the following in the email (I also got the email) :

While these specific issues may not affect every app that uses Apache Cordova, it’s best to stay up to date on all security patches. Apps with vulnerabilities that expose users to risk of compromise may be considered Dangerous Products in violation of the Content Policy and section 4.4 of the Developer Distribution Agreement.

So if you don't update your apps, technically you could get a Google Play account strike after May 2016.

Here's the kicker; I've updated apps in the past for similar issues and the update launches another verification of your app. During that verification there is a reasonable chance that your app will get flagged for a totally unrelated issue and generate a policy strike. It happened to me last time. A 2-year old app got a policy strike for something it was not violating.

So, do we feel lucky?

I had this issue today. You have to make sure the Visual Studio's property page for the Construct project has a target version that matches the installed Windows 10 SDK/Emulator version.

You can discover what Windows 10 SDK/Emulator version number you have by looking in your Add/Remove programs.

After initially getting this error, I selected my correct version number in the property page and my Construct app built successfully in VS Enterprise 2015.

Hi! Visual Studio seems to work now (just Ads dont show up) but I am still looking for any hints how to set the language to English and German and let the app appear with the proper localized name in the store. Any ideas how to do this for Win10 Universal apps?

Hello - did you ever figure out how to run ads in Windows 10 apps? Ive tried pubCenter and AdMob but both dont show ads in the VS emulator.

Seems we are on our own figuring ad issues out as questions for this kind of issue remain unanswered for months.

Hello all,

I am attempting to create a Windows 10 mobile app that is monetized using pubCenter video ads. I created a video ad in pubCenter and entered the details into the Construct pubCenter plugin.

I used the following to show the video ad in my app:

I then exported as a Windows 10 app and then launched the Visual Studio mobile emulator and ran my app. I know that ads SHOULD show in the VS emulator but they are not showing.

Anyone have any ideas as to where I am going wrong?

Thanks!

Moot point - iAds just announced they are shutting shop. Sorry, I wasted my time waiting for feedback that never came.