BlackBerry 6 and 7 application development failure - blackberry

I have successfully setup all the IBM mobile first environment. I then created a mobile app named "BB6APP" with the BlackBerry 6/7 environment.
When trying to run the application build in Studio, I get the following error:
Failed to deploy application 'BB6APP' to MobileFirst Server:
FWLSE3051E: Invalid payload. See additional messages for details.
image of error

Using IBM MobileFirst Platform Studio 7.0.0.00-20151001-1558 I am unable to confirm this. I successfully created a new project, add an application and to the application added the BlackBerry 6/7 environment.
Note that this environment is deprecated - meaning that most likely in the next MobileFirst Platform Foundation release it will be removed.
Try to start over in a new Eclipse workspace
Try to delete the wlBuildResources folder from your TMP directory
Make sure the location you have your Eclipse workspace has full permissions for your user.

Related

Redirect Flutter SDK path when building iOS build?

I wrote a Flutter app using IntelliJ on my Linux machine. I need to build the ipa file for iOS devices, and I do not have a Mac.
I plan on using a "Mac in the cloud" server to prepare the release build for the App Store. I have been mapping out all of the steps that I need to do to do the whole process, and I got to wondering: if I am opening my project folders on a server somewhere, do I have to configure the path to the Flutter SDK that I will have to download on to server machine?
I have looked at the Flutter.io documentation, but did not find an answer to this question.
Goal: to generate a release build for iOS on server machine from the project folders that I used on my Linux machine to make release build for Android.
Well, to answer my own question, IntelliJ seems to find the correct flutter path on its own somehow. It give me an error message after build command, but then continues using correct flutter path. I am pretty sure that I never told the program where to find flutter.

How to deploy MobileFirst CLI application to an IOS device?

I am using MobileFirst CLI 7.1. I want to deploy my MobileFirst CLI application to an IOS device. How can I do that?
I navigated to the iphone environment and tried to double click the .xcodeproj. In the XCODE I see that the project is still being shown as library.
I am getting this following error when I try to deploy the application,
. I have gone through stackoverflow questions. None of them were helpful.
I want to know how can I target remote server. (In Studio we had an option to deploy to remote environment.)
You already asked the second question: How to deploy MobileFirst CLI application to an android device?. The answer is still the same:
Also I want to know how can I target remote server. (In Studio we had an option to deploy to remote environment.)
In the Studio you did not have the option to "deploy to a remote server". You had the option to configure the application to point to a remote server (the properties you can edit in the worklight.plist(for iOS) / wlclient.properties file (for Android).
This feature does not exist in the CLI. After building the project, in case you want it to point to a different server, edit the properties in said file(s) to point to the remote server.
The first question is unclear.
I have done the following and was able to launch the project in Xcode and run the app in the iOS Simulator:
mfp create myproject
cd myproject
mfp add hybrid
added an app called "test"
mfp add environment iphone
mfp push
opened the project folder and navigated to apps\test\iphone\native, followed by double-clicking on the .xcodeproj file. The project opened in Xcode successfully and I then clicked on the Run button, and the app launched in the iOS Simulator.

No IPA output for Cordova build in Visual Studio

I'm developing a mobile app with Visual Studio Tools for Apache Cordova CTP 3.1 in VS 2013. I have configured everything according to the MSDN specifications here Install Tools to Build for iOS. I am able to build the app and run the remote simulator (as described here Run Your Apache Cordova App on iOS).
My problem is there is no output from the build back on the Windows machine where I have Visual Studio. More than that, there is no .ipa file created on the Mac either. I can find the build at /Users//remote-builds/builds/ but that's all. I can open the project in XCode for instance, but that's not what I want.
I want the final package file that I can install on test devices and eventually publish to the store. How do I get that?
Also my goal is to setup a TFS build definition so I can get a build each time I commit changes. I need to get that output file to the drop location of my build.
From within VS, you will have to choose "Remote Device" or "Local Device" as your debug target and then "build" to get an IPA back.
Also, refer to TFS build does not copy Cordova project output for instructions on how to setup TFS for CI workflow.

Worklight Studio 6.2.0.01 in Ubuntu not creating .xcodeproj

I'm using Worklight Studio 6.2.0.01 in Eclipse Luna and Ubuntu 14.04 (Also tested it in Ubuntu 12.02 and Eclipse Kepler).
I've followed the following steps to create a hybrid application with the iOS environment:
Create a Worklight Project
Create a Worklight hybrid application
New Worklight environment (iPad)
Run as -> Build All Environments
Run as -> Run on worklight development server
There are no errors in Worklight nor Server console
Problem: the native folder inside apps\my-app\ipad\native contains only 2 folders, and there's no [project].xcodeproj.
Resources (empty)
www
Native Resources -> Resources (empty)
Tested in Ubuntu and the iPhone environment's native folder was properly created.
As you wrote in your question, please double-check again with these more-precise steps:
Close Eclipse
Make sure you delete the tmp\wlBuildResources folder
Open Eclipse
Make sure the above folder is re-created
Create a project + app + iphone environment

Integrating Crashlytics build script with Xamarin.iOS

I am trying to integrate Crashlytics with Xamarin.iOS. I have successfully added a binding and started the logger with my API key. I'm able to crash the app but no reports are landing on the web dashboard. When adding Crashlytics to an xcode project it prompts you to add a build phase task to run a script (Which I believe uploads your symbol files to their website).
./Crashlytics.framework/run APIKEY
After creating a binding of the framework for Xamarin this doesn't work as expected... I haven't added a build task in Xamarain Studio but running the command from the terminal yeilds:
MacBook-Pro:Crashlytics.framework user$ ./run APIKEY
2013-09-04 16:10:49.941 run[9238:707] Crashlytics.framework/run 1.2.3
2013-09-04 16:10:49.943 run[9238:707]
Crashlytics: Failed to Detect Build Environment
BUILT_PRODUCTS_DIR value not found in environment
So finally the question:
How do you integrate this build script into the Xamarin environment? Do I need to copy more assets around to trick the run command into thinking all is well?
Latest versions of Xamarin Studio support Crashlytics out of the box:
We had been using Crashlytics with our Xamarin project. But, it seems with Xamarin.iOS 8.6 and/or Xamarin Studio 5.7 it is no longer supported, and the Crashlytics APIs have changed.
Here are the steps I used.
In the Xamarin Studio , go to the touch container and add the Crashlytics API key in the Build -> Crash reporting section. Build and run that app. The evidence suggests that is enough to get data sent to Crashlytics. I saw that it knew about older versions of the app I had built and ran weeks ago with the API key already in.
Go to Xcode and create a new project with the same name as the Xamarin project, com.{company}.{appname}. (You probably need to have that profile downloaded.) I did it in Swift by the way with no issues.
Go to crashlytics.com com and go to settings -> Apps (or https://www.crashlytics.com/onboard)
You will get an app to download and run. The app walks through the steps of adding
A build phase run script
Code to the application main Crashlytics.startWithAPIKey(“nnnn”)
Run your Xcode version of the app
The Crashlytics web page popped up immediately.

Resources