Environment: Worklight 6.1.0.2
We have created a hybrid app using Worklight 6.1 for android, iOS and windows8 platform. We would like to include license documents and notices files as part of the app. To do this, we would like to know, if including these documents inside the "legal" folder (under application name folder) and installing the app on the device, will also install these license documents on the device ?
I browse through the android app, but didn't found these documents as part of the build.
The legal folder is not part of the generated Android project because it has no value there. The native project will become your .apk - the file that you distribute to your end-users. The license is of no use there; your customer cannot see it.
Related
my apk is 1.4MB but error is "This APK results in unused code and resources being sent to users. Your app could be smaller if you used the Android App Bundle. By not optimizing your app for device configurations, your app is larger to download and install on users' devices than it needs to be. Larger apps see lower install success rates and take up storage on users' devices."
how to fix this error
It's only a warning, not an error.
For an app that small I wouldn't worry.
It's not something that's made its way into the Ionic ecosystem yet but I heard that if you open up your project in Android Studio and then do the build through there you can create an app bundle.
I'm not totally sure that its fully tested for Ionic so you might have issues with this, but Android have published a full guide:
https://developer.android.com/guide/app-bundle#get_started
This is what they say:
Download Android Studio 3.2 or higher—it's the easiest way
to add dynamic feature modules and build app bundles.
Add support for Dynamic Delivery
by including a base module, organizing code and resources for configuration
APKs, and, optionally, adding dynamic feature modules.
Build an Android App Bundle using Android Studio.
If you're not using the IDE, you can instead build an app bundle from the
command line.
Test your Android App Bundle by using it to generate APKs that
you deploy to a device.
Enroll into app signing by Google Play.
Otherwise, you can't upload your app bundle to the Play Console.
Publish your app bundle to Google Play.
I am using Expo’s managed workflow. My app uses google authentication to sign in. During development I was using the Expo client for android and as per the docs I used 'Expo.Google' to achieve google authentication and it worked as intended.
After developing the app, I built a staging version of my app (standalone app) by typing 'expo build:android -t apk --release-channel staging-v1' in my project directory. After the build was finished, I downloaded and installed the apk on my android phone. Only then I realized that I didn’t change 'Expo.Google' to 'GoogleSignIn' which is required for standalone apps.
I can change that in my project files and then publish it to the staging-v1 channel. I think this would make google authentication work in the standalone app but it would also change my project files and then it won’t work in the Expo client. So, do I need to create and maintain two different project folders which would basically be the same except for the google authentication part? In general, how should I manage the channels and the corresponding project files?
I am using IBM Worklight 6.0 with December 14th fix.
I am trying to use IBM App Center client for iOS8.
I have seen multiple discussions about this issue:
IBM Worklight Application Center iOS unresponsive to touch events
IBM App center not working for iOS8
I copied the project from my server, where the fix is installed, and built for iOS, but when I inspect the mobile App, I can see that the application is using Dojo 1.9.0.
> dojo.version.toString();
"1.9.0 (29469)"
I can see that the IBM App Center mobile client does not use Dojo Toolkit, but includes a dojo.js file (with a size of 1.2MB).
My question is : What are steps to build IBM App Center for Worklight 6.0, knowing that the fix is installed (Both Worklight studio and server)?
Do I need to manually change dojo.js file with a newer version? if yes, where can I find such file?
The AppCenter installation contains an Application Center Installer application project.
This is a Worklight project with the iPhone environment. The app that is generated from it is the Installer application that you need to install on a device, and from which the user will then install any subsequent applications distributed via Application Center.
Make sure you are using the provided Worklight project; there are no additional changes to be done to to project (other than using your own bundleId, ...).
It could be that you are missing the Dojo library in your workspace?
You can generate it by creating a new Worklight project and application using the Dojo wizard in Studio.
When you received the fix, it contains a new project for IBM app centre.
You need to get this project and import it to your Eclipse Environment and rebuild the IBM app centre (APK and IPA) files.
You have to redeploy these files to IBM app centre console and re-download them on your iOS8 devices.
I believe the iOS8 fix starts from version V6.2, and we have downloaded fix v6.2.0.1.
So, I'm not sure about V6.0.
Please verify with IBM.
Has anyone tried the "Android - Adding native functionality to Hybrid Application using Apache Cordova plug-in" feature in v6.2 ?
I'm trying to use a 3rd party library on the client side and wanted to understand where to put the plug-in java class in the project. The documentation shows a java package (src) structure whereas the best I can find is normal folders in the android native folder.
Thanks.
The reason you see these as "regular" folders is likely because you are look at the Worklight project rather than the generated Android project.
Worklight project\apps\your_app\android\native\ ... will look as folders because they are indeed just folders.
Once you build your Worklight application (containing an Android environment), an Android project will be generated. In it, you will see the folders as packages, etc.
A Worklight project and application structure is explained in earlier training modules:
Creating your first Hybrid Worklight application
Previewing your application on Android
So, you should place your Java Class file in Worklight project\apps\your_app\android\native\src\com\package_name\ ...
Note about Cordova plug-ins in Worklight: depending on the plug-in this may not be possible to use as some plug-ins require using the Cordova plugman, which is not yet supported in Worklight.
My environment :
Eclipse sdk 3.7.2
Worklight pluin 5.0.5
Android sdk 2.2
First I tried a simple Hello World, everything works fine, android native project was created and I see the corresponding apk file was generated after a build and deploy.
Next I imported a sample project, successfully got it run on the test (localhost) server, able to see the expected result on the android Mobile Browser Simulator but the problem now is I am not seeing the corresponding android apk file got generated (the android native project was created). No errors on the logs, Any idea what could be the problem? How one debug such a problem.
APK will be generated under \bin\ folder once you run your app for the first time.
Connect your Android device to dev machine via USB cable (assuming you got Android SDK etc installed), right click on Android project and do Run as->Android app.
The app will be installed and started on Android device. APK will be generated in \bin folder.
In general, you don't need the device, same thing can be done with emulator.
You can also do an export on the android application project. This is what you would do if you are looking at doing some key signing. This is the way you would want to export it if you are uploading to Google play or an enterprise app store.
Keep in mind, Worklight doesn't build your .ipa, .apk, or etc. It builds you compile ready resources. It will build you the folder structure and the project layers needed to build in the corresponding Native Environment (for apple, you would export to xcode, build it, and run).