I'm getting the below error, while deploying wlapp of Maximo Anywhere in development server.
Direct update is not working though the wlapp has been deployed.
FWLSE3210W: Environment: iphone of application sampleApp version 7.5.2.0 has been deployed with a different version of the native MobileFirst SDK. Direct updates will no longer be available for existing clients with other versions of the MobileFirst SDK. To continue to use direct updates, increment the app version, publish it to the public app store, deploy to the server, and (optionally) block/notify older versions of the app to enforce customers to upgrade to the new version from the app store.
Any ideas?
Need to manually stop auto upgrading the MFP if you are not using latest SDK. upgradeMFP will upgrade the mobile first SDK . workaround was we created new war and deployed new wlapp, ipa to made direct update to work
Related
I already have an app on app store with version 1.0.0.
Now I submitted the new version of app 2.0.0. This new version is also approved by apple.
It has been more than 5 days since my app is approved and in state 'Ready for sale'.
Now when I download the app from app store on my iphone device it still downloads the previous version (1.0.0) and asks me to update to latest version (2.0.0).
Why app store is not downloading the latest version (2.0.0) of app directly on my device?
My device previously had the app with version 1.0.0 installed from app store but I deleted it and then installed the fresh app from app store.
When I download the same app on my friend's iphone it downloads the latest version (2.0.0). This device never had any version of the app installed.
I had the same problem and have now realised that it is related to iCloud. If you have previously downloaded your app on any device then when you download it on a new device, it will download the same version as you previously downloaded. You then get the option to update to the latest version.
Confused me to start with!
Your iPhone could be outdated / not meeting your defined requirements of the application itself. For example, if you have an iPhone 3G running IOS 6, you can not run an app that only accepts iOS7. Take a look in your xCode and inspect the properties of your application.
i want to know what things need to be do in developing the upgrade version of an application (like bundle version) so that if a user download my upgrade version of my application then it update the old version.
i have develop the upgrade version of my app in old version and just changed its version no. I need that data of my old app remains there.
All data in the document directory will not be touch when upgrading. All files in the bundle will be copies from the new version.
IF I set the deployment target for my app to iOS 4.2 when submitting to app store, will users with iOS 3.2 (or anything below 4.2) be able to download and install the app and the app won't run or will they not be able to download and install the app itself?
Thanks.
They won't be able to install and run the app (until they upgrade the OS on their device to that of the Deployment Target or above). But they might be able to buy and download the app using iTunes on their Mac or PC.
No, that's exactly what deployment version is about.
Best practice is to build against latest SDK version, with deployment version as low as possible. But that requires the discipline to do runtime checks and fallback implementations whenever using a API that wasn't there yet in the deployment version.
I'm testing my in app purchase code for an update to my app. The in app purchase works great when I do an install from xcode to my phone. The issue arises when I have the currently released version installed on my phone then I install the dev version over the top of the release version. When I install in this way my product ID comes back as invalid even though I've tested it many times and it works as long as I didn't have the release version installed previous to installing the dev version.
We did alter our Bundle ID in this update but everything has worked except when we install in the way I described above.
Has anybody encountered this behavior before?
Also the currently released version does not have in app purchases.
This happens all the time.
If you install your development version over the App Store version - new In App Purchases IDs are returned as invalid.
This will work perfectly when you upload the new version to the App Store.
I downloaded a pre-release version of the iPhone SDK and tried to update one of my existing apps using a binary I built with it. Obviously you are not supposed to do this but I had forgotten about the warning when I installed the pre-release SDK. Anyway - I have two questions:
Can I simply set the base SDK to an earlier version in the build settings and get around this problem?
If not, then what should I do?
You need to download the release version of Xcode with the release iPhone SDK. You can't use the SDK downloaded from the iPad beta version for any release products.
Just go to http://developer.apple.com/iphone/index.action and click on iPhone SDK 3.1 and download it. Then build your app bundle with that and submit it to Apple.
Before you download a pre-release version of the SDK from developer.apple.com, there are several prominent warnings, one of which clearly states that pre-release versions of Xcode / iPhone SDK can NOT be used to build production binaries. So the answer to 1. is an emphatic no.
As far as I can tell, the only option to be able to build production binaries that iTunes Connect will accept is to delete the pre-release version of Xcode / iPhone SDK and re-install the older stable version.
If you upgraded using the beta download (as opposed to installing on a fresh box that has never seen SDK or Xcode), set the base SDK to a released version of the OS. Compile a Distribution build, submit to the app store. The old SDK is still there, so that will get used. All of the prominent warnings I have seen state the the SDK cannot be used, without mention of Xcode.
Before anyone scoffs, note that I submitted an app on March 13 using the version of Xcode (3.2.2) included in Beta 4, setting Base SDK to 3.1. It was approved on the 15th. I've also done this during the 3.0 beta for 2.x apps.
EDIT: on the other hand, acceptance apparently isn't always guaranteed (note that this person had also submitted an app that did get accepted): The binary you uploaded was invalid. A pre-release beta version of the SDK was used to build the application