Testflight Invalid build while using Mobile Quality Assurance - ionic-framework

I am new for ionic i added "Mobile Quality Assurance" sdk using below the tutorials
SDK Downloads : http://www.ibm.com/support/knowledgecenter/SSJML5_6.0.0/com.ibm.mqa.uau.saas.doc/topics/IOSSDKsForDownload.html
Installation - http://www.ibm.com/support/knowledgecenter/en/SSJML5_6.0.0/com.ibm.mqa.uau.saas.doc/topics/t_InstallingTheIOSLibraries.html
and my project contains "MFP" Plugin
Now the app is working well on devices, but if i uploaded to app store i am seeing "invalid binary"
Note: Before implementing "Mobile Quality Assurance" build shown on preparing for submission.

It is unclear what is the version of the IBM MobileFirst SDK you're using, but since you say you're using Ionic as the platform for creating your Cordova application, you may be using v8.0 of MobileFirst, in which case MQA is not supported. See here for more information: IBM MobileFirst Quality Assurance - MQA Not Defined

Related

Can't run app on Huawei lite wearable (GT2 PRO): API error when installing on device

I am trying to write an app for my GT2 Pro but when I try to install my app with Huawei DevEco Assistant, it gives me the following error:
Installation failed: 47. Invalid value entered for app.apiVersion
Here is the steps I did:
I created a [Lite] JS project.
I signed the app without any changes on project.
I built a signed hap and copied it to the haps directory on the phone.
I tried to install app via DevEco Assistant.
DevEco Studio details:
DevEco Studio 2.1.0.501 with api 4-5
DevEco Studio 3.1.0.100 with api 4-7
I assume you followed the process for debugging your app on GT2 Pro at https://developer.huawei.com/consumer/en/doc/distribution/app/agc-help-harmonyos-debugapp-manual-0000001177608893, especially on Sports watches section.
What's the software version in the GT2 Pro? If it has been upgraded to the latest version, you need to check the build.gradle file and ensure the SDK version is correct. For the lite-wearable device, the compatible API 4 and target API 5 are recommended. You may set API 4 for both or API 3 and API 4, depending on HarmonyOS version in your device. You also need to make sure the API configuration is consistent in the config.json file if the "apiVersion" is configured. In addition, you should use the official released DevEco Studio such as version 3.0 or version 2.1 for your app development and debugging.

How to build mobile website with ionic 1.2

How does one build a mobile website with ionic 1.2? I can't find any official guides/tutorials/docs.
This is an excerpt from a post on the ionic blog announcing ionic 1.2 release:
Ionic 1.2 marks the first release where we actively recommend Ionic for those looking to build a mobile website (not just an app for the app store)
Well, there's nothing stopping you from deploying it as a web app, as long as you don't have cordova dependencies in your app (for the natives). Also be aware that non webkit based browsers will probably malfunction.
Look at this thread for testimonials with mixed results

Using Ionic to develop IBM MobileFirst Platform hybrid applications

I have mobile first development studio in my eclipse and by using that I created a new MobileFirst project and hybrid application. Added an Android and IOS environment to the application. I have idea of worklight. Ionic support is added using mobile first 7.1. How to install ionic? I have read many steps using all CLI based. Can any one guide me to install process of ionic.
It is not possible, or at least easily possible to use Ionic with a MobileFirst Hybrid project that was created in MobileFirst Studio.
Instead you should create a "pure" Cordova application, that uses MobileFirst's SDK.
You can read more on this in the following blog post: https://developer.ibm.com/mobilefirstplatform/2015/04/16/an-overview-of-using-the-ionic-framework-with-mobilefirst-hybrid-mobile-applications/

Worklight Facebook platform selection?

For Facbook integration in Worklight which platform should we select Android or Website
,
right now i am developing for android environment but later i will be doing for iphone and windows as well
Also were do i place the Facebook integration code in index.html(main) or in android project which is separately created ?
i am confused do reply
It looks like you are developing a Worklight-based Hybrid application, so in this case you should actually opt for the Facebook JavaScript SDK.
You can add it to your common\js folder and reference it in the common\index.html (just follow the instructions Facebook probably provides). This way you could easily 'extend' it to whichever additional environments you will add in Worklight Studio in your project setup.
Of course, you can also choose to use Facebook's native SDKs for each environment in your Hybrid application. In this case, you'll need to add the SDK in the iphone-ipad-or-android\native folder and follow Facebook's integration instructions (note that for iPhone the actual integration will be done in Xcode, not Eclipse).
If you choose to create a native application and bundle it with the Worklight SDK, then you should opt for the Facebook SDK dedicated to the specific OS. Here, you will add the SDK, again, by following Facebook's instructions.

Missing platform support?

I want to connect an existing PhoneGap application to a newly created mobile service in Azure, but in the dashboard for the service I'm only presented with these three choices for the "Choose A Platform" option:
Windows Store
Windows Phone 8
iOS
Where is Android, HTML/JavaScript, Xamarin and the new PhoneGap option?
I take that you created a new mobile service using the new .NET backend. For now, the quickstart (starter) projects for that platform are only available in the four versions you see there (WinStore C#, WinStore JS, WinPhone 8 C#, iOS Objective-C), and others will be added soon.
However, the backend still supports other platforms (HTML/JS, PhoneGap, Android, Xamarin), it's just that we don't have the starter projects for those in the portal yet. You can take one of the supported ones, download the server project, and create the client project to talk to it.
Again, all supported platforms will get their quickstart projects added soon.