Closed bug still live ( or possibly reborn )

ionic-v1
1

using CLI 2.2.3 to create a v1 project
when do;

cordova platform add android

get;
Adding android project…
Creating Cordova project for the Android platform:
Path: platforms\android
Package: com.ionicframework.ion1193413
Name: ion1
Activity: MainActivity
Android target: android-25
Subproject Path: CordovaLib
Android project created with cordova-android@6.1.2
Error: Source path does not exist: resources/android/icon/drawable-hdpi-icon.png

when do
ionic resources

get;
Ionic icon and splash screen resources generator
icon source file not found in any of these directories: resources, resources/android
valid icon source files: icon.psd, icon.ai, icon.png
splash source file not found in any of these directories: resources, resources/android
valid splash source files: splash.psd, splash.ai, splash.png
Unable to generate images due to an error MISSING_SOURCE_FILE

I just created this project and I expect it to have default resources

(this issue was discussed over a period of about 10 months at


before being locked)

2

This is quite an old version.
What does cordova -v output?
Anyway, you should update your cordova installation so you also get a newer cordova-android when you create projects.

3

November 2016 and works with everything else (that I’m currently using).

Now, with the current state of frameworks floating around these days I like to STAY with something that works until I NEED to upgrade - see any number of posts on having to revert back - hours lost because when you live on the “cutting edge” you tend to bleed a lot .

THIS IS A PROBLEM WITH IONIC ; I followed all the instructions and it doesn’t work and it hasn’t worked reliably for almost a year ( read the linked thread ).

Maybe turn off your Jenkins and wait till you’ve got it working before you release.

The reason I was looking into ionic 1 is because ionic 2 (even on recent devices) is SLOW and BIG and hence not appropriate in all BYOD situations. AND MY GOD ! take a look at where the timer values are set for telling you the time to deviceready - WAYYYYY after the page load starts - talk about marketing spin !!!.

SO YEAH - use CROSSWALK - another 25 MB …to the APK! plus about another 75MB in RAM when running - and it DOESN’T start faster - it caches rt info so the 2nd start is quicker. Try having 2 or 3 crosswalk apps on a device with wifi etc (under normal load) - better get reading on object c and the android sdk coz it’s not practical.

But HEY ! all this crap has me going back to vanilla cordova for this app.

Cordova - write once, run anywhere. Ionic - write once, run anywhere…on an iPhone.

4

Were you using Angular 4 and AoT (–prod) mode? In my experience, those two things make a substantial improvement both to app binary size and launch speed.

5

Well, you opened a topic with a report that something doesn’t work. As you mentioned you created a new project, updating everything to the current version should be a no-brainer - that’s why I suggested it.

Good luck with the Cordova project.

6

Eons ago ! ( 2 - 3 months ionic 2.2.1 ) so Angular 2.

Just an empty project ;

Development build was (as far as I recall) 12 -14 seconds on both a 5th Gen Kindle with wifi off and a Samsung S3 airplane mode/wifi off - neither running anything much else.

Prod mode as you say brought this down significantly - about 4 secs to deviceready which is still a long time.

So even with AoT the first thing on my list of todos for an ionic 2 app was (still is) to look into cutting that time or making it seem like less to the user.

Now, to be fair, start up is a problem with cordova generally and putting the app in the background rather than exiting is a solution once started but that first time start of 4 secs is a credibility issue…

7

FWIW, I saw startup times cut roughly in half with no codebase changes simply due to the Angular 4 swapover.

8

Thanks. I’ll look at it again.

9

I’m using cordova 6.5.0 which adds cordova-android 6.1.2

This was the most recent official version of cordova until 5 days ago when
cordova 7 was released.

5 days in is too early for me to trust it.

Presumably corodva-android builds prior to cordova 7 should all work with cordova 6.5
which means there is ONE (official) cordova-android build since 6.1.2 ; 6.2.3 ( there were 4 official releases on the same day )

Anybody using Cordova 6.5 - which will be most people - will be using cordova-android 6.1.2

Anywho…

As per your suggestion I ran ;

C:\ion1>cordova platform rm android

C:\ion1>cordova platform add android@6.2.3

with the following result ;

Adding android project...
Creating Cordova project for the Android platform:
        Path: platforms\android
        Package: com.ionicframework.ion1193413
        Name: ion1
        Activity: MainActivity
        Android target: android-25
Subproject Path: CordovaLib
Android project created with cordova-android@6.2.3
Error: Source path does not exist: resources/android/icon/drawable-hdpi-icon.png
```
So no change there.

Running the same commands on a vanilla cordova hello world worked as expected with no errors.

For now going to look at ionic 2 again in light of rapropos's comment.