Do I need to delete development plugins before publish my app? - android

I am just about to finally publish my ionic app on android. I was reading the ionic documentation about how to publish the app and at some point it mentions that I have to delete some unnecessary plugins that are for development before releasing the app.
My question would be, is it really necessary? I mean will it make a difference if I don't remove it?
" So first, we need to generate a release build of our app, targeted at
each
platform we wish to deploy on. Before we deploy, we should take care to
adjust plugins needed during development that should not be in production
mode. For example, we probably don’t want the debug console plugin
enabled,
so we should remove it before generating the release builds:
$ ionic cordova plugin rm cordova-plugin-console "
reference: https://ionicframework.com/docs/v1/guide/publishing.html
Thanks in advance

You are referring to v1 documentation, but you have tagged ionic4 in your question.
As you are new I'm going to assume ionic4 is what you are really targetting.
The most up todate Android publishing docs are here:
Android Play Store - Ionic Documentation
The system that v1 used was very different to modern Ionic. There may be some advanced customisations that you can make but by default, you don't need to remove plugins before you publish.

Related

can i built an iOS app after creating it's android version's apk on same project on Flutter?

i have just finished coding of my android app and it is time to built it's apk but i want to create it's iOS version ipa to. i know i have to work on XCode on MAC for getting it's ipa output but i don't have any iOS device. nothing about Apple. so i want to use alternative ways like CodeMagic but i am new on development so it seems creating an ipa output will take a long time for me. in addition i didn't make any stuffs needs to be done for an iOS app can launch. for example i am using Firebase services but i only made it's android settings, didnt set anything about it's iOS version. so i have to do lots of things for creating my flutter project's iOS version and need time. at this point i have a question:
Can i built my app's iOS version after creating it's android version without make any settings for iOS? i want to built it's android apk or appbundle as soon as possible and i want to do it's iOS settings and built it's ipa later. is that possible? thaks for your helps.
Based on my experience... you'll have to setup the iOS separately to successfully build it.
For example when using firebase you'll need to add the GoogleServices file using Xcode.. or when using google maps you'll also need to add the api key on the appdelegate file.

Distributing Flutter with Fabric to beta testers

My company is trying out Flutter to create mobile applications and I'm currently in the process of trying to distribute both iOS and Android beta builds through Fabric.
The flutter plugin repo doesn't have any Fabric plugins and I can't seem to find any guides at the flutter home page nor elsewhere online on how to achieve this.
I had planned to focus first on iOS since I'm an iOS developer and figure android out later and use fastlane-match to manage my codesigning on iOS. What I've come up with so far is that I'm gonna try to create post-build-scripts discussed in this fabric guide and thus upload my builds manually after flutter builds and creates an IPA file. I'd say this is not optimal since it differs from the rest of our build setup, as in the fabric kit is not directly embedded in to our iOS project.
So I'm wondering if anybody has any experience in distributing flutter apps with Fabric and if you had any tips on how to achieve this, preferably with Fabric integrated into my iOS and android project respectively.
Edit:
For anybody interested in the solution, I ended up adding the Fabric and Crashlytics cocoapod into the generated cocoapod file by flutter and installing them via pod install. I'm not sure if that cocoapod file will get overwritten in the future as my experience with Flutter is quite limited.
After that I was able to import both Fabric and Crashlytics into my AppDelegate and Initializing the Fabric kit from there just like in a normal iOS project, as well as adding the runscript phase and plist entries as recommended by the fabric iOS install guide.
I also set the project up to use manual code signing and managed the codesigning with fastlane match.
After that I created a fastlane script that uploads to crashyltics. The build script I ended up with is:
flutter build ios --release --no-codesign
cd ios
fastlane ios beta
where ios references to my platform and beta is the name of the lane that exectues the fabric upload. The beta lane first builds with gym (to sign the IPA file) and then that signed IPA file is uploaded to crashlytics.
Fabric is now integrated to Firebase. It was deprecated after March 31, 2020. With this, you can now refer to Firebase App Distribution as an official documentation.
Flutter also has a bunch of documentation regarding distribution of Flutter applications to beta testers.
Continuous delivery with Flutter
Follow continuous delivery best practices with Flutter to make sure
your application is delivered to your beta testers and validated on a
frequent basis without resorting to manual workflows.
You can also check this blog for some useful tips and more information on Deploying Flutter apps to Firebase App Distribution using Fastlane:
Deploying Flutter app to Firebase App Distribution using Fastlane
In this article, I will be showing how to set up and deploy your
Flutter app to Firebase App Distribution with the help of
fastlane.

Deploying Ionic app to the Google store

I'm trying to deploy my first (very generic) app built using Ionic. According to the docs for deployment, I'm supposed to use some plugins. However, other sources suggest that I'm supposed to install Google's IDE called Android Studio and create an APK file.
I can't judge which approach is most valid nor if the one is an obsoleted version of the other. And we know how fast the wheels rotate in JS world...
NB. I'm confident in programming in general, I know Angular and have experience with deployments as such. In this case, I'm not looking to set up CI nor testing. I simply want my first app to be reachable through the store.
My suggestion would be to make a build: ionic cordova build android. Next sign it using the command line.
https://developer.android.com/studio/publish/app-signing.html

Cordova Release App to Play Store Issue

I have generate a signed help.apk file but when I publish the app on the Play Store, I got a mail with this issue:
The vulnerabilities were fixed in Apache Cordova v.4.1.1 or higher.
Edit:
Freshly built project with File, File Transfer and Splash screen plugin added to it. Older versions of this app are already successfully in play store; I am just upgrading Cordova version and applying some minor fixes.
Android version - android 6.1.2
Cordova version - 6.5.0
Yet, google play rejected my app saying:
This app uses software that contains security vulnerabilities for users or allows the collection of user data without proper disclosure.
The vulnerabilities were fixed in Apache Cordova v.3.5.1. You can find more information and next steps in this Google Help Center article.
Can anyone help with the solution to this rejection?
You need to update your cordova-android platform to 5.X.X.
To Update cordova-android platform
cordova platform rm android
cordova platform add android#5.x.x
follow this link for more details https://cordova.apache.org/announcements/2015/11/20/security.html
Since no one is posting correct answer, i'll add what works for me.
Kerri Shotts comment helps me a lot. yes, you should look at your 'www' project more closely and remove previous 'cordova' js files inside it. Let the cordova build to add them.
Do necessary changes in your html files to use latest cordova.

APKs generated through Eclipse are accepted or not?

I am a little new to Android development.
I have a hybrid app which uses Apache cordova plugins.
I am using eclipse to generate the APK.
But when I publish the APK, the Google play store rejects it saying:
APP UPDATE REJECTED
Your APK has been rejected for containing security vulnerabilities, which violates the Malicious Behavior policy. The Alerts page has more information about how to resolve the issue. If you submitted an update, the previous version of your app is still live on Google Play.
And, when I click on the alerts page the following error shows up:
Security alert :
Your app is using a version of Apache Cordova containing one or more security vulnerabilities. Please see this Google Help Center article for details, including the deadline for fixing the app.
I have already tried the followings:
Update the android platform (cordova platform update android), but no positive results.
I could not update all the cordova plugins as I am getting errors. (wanted to know can this be the issue)
I am building this APK using the Eclipse IDE and I went through this ADT plugin release note https://developer.android.com/studio/tools/sdk/eclipse-adt.html which says: The Eclipse ADT plugin is no longer supported
Eventually I will be importing my project to Android studio but I want an app update immediately thats why still using Eclipse.
If Eclipse is the reason then I immediately need to import my app to Android studio.
I want to figure out that which one of the last two point is responsible for my app rejection.
Also, if none of these are responsible then what could be the possible reason for my app rejection.
Thanks in advance.
An APK is an APK, regardless of where you developed the code. You can write the code in Eclipse, Android Studio, or you can write the code in your favorite plain text editor. The end APK will be indistinguishable regardless of which editor you use.
The error in this case seems to be pretty clear- your version of Cordova has known vulnerabilities and you need to update that.
Run cordova platform version android to check your version. The error message you are receiving will show for anything less than 4.1.1.
The best path would probably be to upgrade to 5.x, as detailed here.

Categories

Resources