I have worklight app project on my local, one of my colleague has already deploy app on Worklight Server 6.1, he provided me apk and ipa both, I have installed ipa in my iPhone.
Now when I do some changes in the code for that app and deploy it doesn't give me update in my iPhone, i tried another android device but the update is not coming on that also, This work perfectly when I access my browser console (server console) for that app. but for device its not working
I have worklight studio 6.1, Server 6.1. While deploying i am giving correct URL and context, and on server console updating .wlapp for all environment.
I checked with my colleague and he is doing same step and when he updates something and deploy it works but when I do it doesn't
Please let me know what I am missing here
Thanks
Your explanation has many holes in it, making it difficult to understand your scenario. You need to explain it better and with far more detail about your environment, about your colleague's environment, about how s/he and you are building the project and where to you are deploying it.
Edit your question with the above.
Trying to understand what you wrote... do you mean that:
You have some Worklight project in your local Worklight Development Server (Worklight Studio).
You provide the project to your colleague who does... what with it? builds it? Where? in his OWN Worklight Development Server? and then provides you the .ipa and .apk?
To where does you colleague point the app? to his own server?
If you install an .ipa or .apk that points to server X (your colleague's) and the you build it again, in your own server, and do not point it to server X as well (AND deploy the .wlapp in server X), you will never get the update in the device.
You need to make sure what is the serving Worklight Server for the application.
You need to make sure to build the application and deploy it for that server.
This you set-up in Run As > Build Settings and Deploy Target.
You need to then Run As > Build application, and the deploy the generated .wlapp to server X
Then, the installed app will receive an update.
Related
For automation testing purposes presently I am downloading the latest build from appcenter and storing it in my local. And in the script I am getting it installed on the android device. But this will not workout when I want to run the script through pipeline.
Is there any way to get the apk downloaded directly from appcenter and have it installed into the device.
App Center is a continuous integration, delivery, and testing solution for Android, iOS, macOS, and Windows apps. App Center let developers to ship apps faster and with more confidence by automating the development life cycle.
You can't directly download from app center and install it to android device. But you can upload your application binary package to app center and distribute it. You can distribute releases to individual testers or groups of testers. Azure DevOps uses the App Center Distribute Task for this.
Check Build, test, and deploy Android apps - Azure Pipelines document for more information.
This might be helpful in your case if you would like to upload the build from app center and run your test on real device or simulator:
https://www.browserstack.com/docs/app-automate/appium/integrations/app-center
I have a Question regarding side loading apps created with React Native (Expo).
I have build my app and uploaded it on the Expo Servers. I managed to side load the App on an Android Device without any problems. Even Over the Air updates run perfectly!
Now my question is if someone has ever managed to side load an app on an IOS Device? Is this even possible?
Its pretty simple on Android but as I know IOS it wont be easy on there because they always make your life extra hard :D
If someone has a guide or some reference on how to side load an Expo app I would really appreciate it.
Edit: I checked out this link: https://docs.expo.io/distribution/building-standalone-apps/ - which says that it can be done with XCode somehow.
As I dont have a Mac and I never want to own a Mac is it possible to do this via a VM maybe?
Thanks ~Faded
It's not hard if you have Xcode. There's a few steps here, but it's not difficult.
Do an archive build in Xcode.
Right click the build in Xcode->Archive and select "Show in Finder"
Right click the .xcarchive in Finder frand "Show Package Contents"
Navigate to Product->Applications. There will be a .app file in there.
Connect your phone to your Mac if you haven't already
Open Xcode->Devices & Simulators
Select your phone
Drag the .app from the Finder onto the "INSTALLED APPS". This will install the app on the device
Sorry, just reread the OP. I guess if you can get the xcarchive or .app from Expo you should be able to side load it using the last few steps
There are few options to load app but they require either macOS system or paid Apple developer account.
You can build in xcode if you have access to native sources, so it wouldn't work with expo managed workflow, but it's possible if you eject. (macOS required)
You can create simulator build expo build:ios -t simulator (it will work only on simulator) (macOS required)
You can create adhoc provisioning profile and use it for build, it will be possible to install that app only on devices registered on your apple account. (requires paid Apple developer account)
You can side-load builds if you have enterprise Apple account
I've got a Cordova / Ionic App developed by an external group that we're trying to do some QA testing on. To build out these tests we're attempting to intercept the application with a proxy so we can monitor what API calls the application is making. However, every time we configure the Android or iOS device to use a proxy; the HTTP calls in the application error out.
We have already imported the Certificate Authority of our proxy into the device as a trusted Certificate Authority, and this is confirmed working in the native browser (We can go to SSL sites without any errors/prompts).
The development team is telling us that they haven't done any certificate pinning, or anything "extra" besides what is built into the framework. They are confused as to why our proxying isn't working.
Can anyone tell me what default "platform features" that is preventing our proxying from working, and what we need to tell the development group to give us a build that will allow us to do what we need to do?
Just to be clear, all we have available to us directly is the APK and the IPA file. We do not have the full source-code. We can request the source-code be changed with a new build for us to use; but we cannot just run the Cordova app.
I have a beginners question.
I deployed my meteor website on Galaxy. Now I want an android version of my website. I followed every step in mobile docs. Everything is working fine on windows and the app is working as expected in the emulator.
Now if I build my app for production, we need to give a host and port.
What port and host should I use so I can use the same code base as my website?
Here is My domain
I tried:
meteor build ../output --server http://heybuddy.meteorapp.com:80
But without success. Or do I see it totally wrong.
Thank you for any answers!
The host is where your server is accessible, typically the address you use to access the browser-based version of your application / website.
The port is not mandatory.
I do understand that a .apk file is created in the bin folder of an android project, when the project is run.
I have a question about this: is it possible that there would be any difference in the functionality of an app installed via eclipse (as in connecting the phone to the computer and uploading and installing the app on the phone) versus installing the app by downloading a .apk placed on a secure server?
The reason I ask this question is that I usually put up the .apk file on a secure server and the testing team downloads and installs the app for testing purposes. The testing team has started to report app crashes when accessing this app. However, I don't seem to be seeing the any such problems (even while replicating the same scenarios) with the app when I install it on the phone via a cable connected to the computer.
You might be falling into a caching issue. Make sure you get the QA team a new filename of the apk on the server to ensure that they never get a cached apk when downloading it. Also maybe create a md5 sum of the apk locally and run md5 on the apk on the server after upload to ensure it is the same.
e.g. use
md5 yourapk.apk > yourapk.md5
on your machine and the server..
Most likely you QA team has found issues that are specific to the device or Android platform version they test with. Try with your apk with the same hardware in your dev environment.
I don't see how that would possible. The Eclipse ADT plugin just calls the executables in the specified Android SDK location on your hard drive and the .apk gets generated only once when you use Eclipse to install the application to your plugged phone.
Unless you're packaging the two versions in a different way, that shouldn't be possible. My guess is that your testing team has just found bugs specific to the runtime environment (the phone). Maybe a different version of Android, conflicting custom ROM, etc.
No, there is no difference , if the apk on the secure server is as latest as you have on your computer.
I would recommend you to clean your project before uploading the apk to the server.
Regarding the crashes, i guess there are some location based problems.
Also check if you are uploading the apk from your workspace. or some other older version which is located in different place that you are not using anymore.