We have a mobilefirst 7.0 hybrid application project that includes iOS and android native environment.
We want to use mobile first cli 7.0 on windows 7 to build project and generate build-time resources after we checkout this project from git server.
And it fails when it began to parse info.plist of iOS project.
The error message below is what I got from mfcli:
[Error:
BUILD FAILED
D:\programs\IBM\MobileFirst-CLI7\mobilefirst-cli\node_modules\generator-worklight-server\lib\build.xml:135: The following error occurred while executing this line:
D:\programs\IBM\MobileFirst-CLI7\mobilefirst-cli\node_modules\generator-worklight-server\lib\build.xml:341: The following error occurred while executing this line:
D:\programs\IBM\MobileFirst-CLI7\mobilefirst-cli\node_modules\generator-worklight-server\lib\build.xml:351: The following error occurred while executing this line:
D:\programs\IBM\MobileFirst-CLI7\mobilefirst-cli\node_modules\generator-worklight-server\lib\build.xml:330: Failed building application: com.worklight.builder.exception.WorklightBuildException: com.worklight.builder.exception.WorklightBuildRuntimeException: Resource Manager - Problem reading info.plist file 1-byte UTF-8 �ǦC���L�Ħ줸�� 1�C Nested exception: 1-byte UTF-8 �ǦC���L�Ħ줸�� 1�C
Total time: 18 seconds
]
What does it mean "Resources Manager -Problem reading info.plist file 1-byte UTF-8"?
Our git local repository on windows 7 was set to core.autocrlf = true.
There are Traditional Chinese characters in info.plist file, therefore this issue could be related to character settings.
Use a .gitattributes file to control line endings (do not rely on core.autocrlf) and explicitly exclude plist and other binary files from line ending conversion.
For example:
* text=auto
*.plist binary
The MFP CLI does not change the encoding of files.
It sounds like the Git server - perhaps the fact that it is hosted on Windows - indeed affects the encoding of the files.
The files should be UTF-8.
After further more investigation, we found out that this issue is definitely related to mfcli.
Perhapes mfcli on windows does not accept non ascii code characters in Info.plist. We could fix this problem easily by applying Localized strings for info.plist file in ios project.
Related
I found voip example on github for UWP. Now I'm trying to create my voip app, and I want to use VoipHost project in my app. I added existing project, edited package manifest file. When I want to deploy the app to the device I get error:
Severity Code
Description Project
File Line
Suppression State Error
DEP6701 : Bootstrapping failed with unexpected error: 'The ID value is not specified. Parameter name: id'.
VoipHost
And one warning:
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\AppxPackage\Microsoft.AppXPackage.Targets(1930,5): warning APPX1708: The executable 'VoipHost.exe' is specified as the implementation for the .winmd file. Only in-process servers are supported for generating registration information in the app manifest. You must specify the out-of-process server registration information in the app manifest.
Any advices?
Many thanks.
I had a similar issue deploying a headless application with Windows IoT running in a Raspberry pi 3. I solved the problem giving an "Assembly Identity" in the project properties.
You can do that following the next steps: Rigth Click to project --> Properties --> Manifest Tool --> General.
Fill the field "Assembly Identity" with any number. After that compiles, run and works like a charm.
I'm running ....\bin\vsimporter.exe (with default settings) in my project folder and the .sln file seems to build successfully, but when I try running the simulator (on Win32 Solution Platforms, debug build), I get a bunch of errors. Most of the errors involve a missing file from the iOS 8.4 SDK (sys/types.h):
Error unknown argument: '-Xanalyzer'
Error 'sys/types.h' file not found
Error unknown type name 'XSym'
Am I supposed to include the iOS8.4 SDK? Any help/suggestions would be great.
I had the types.h problem too. Try to manually retarget to the Win 10 SDK:
Right-click on the solution and hit retarget, select the latest Win 10 SDK from the list, select all projects and click ok. The types.h problem should be gone.
Retarget answer worked for me to get rid of the errors with missing header files.
To get rid of the -Xanalyzer issue, I removed it from the .vcxproj file as a command line option using a text editor.
For the pods, I manually copied them from a Mac that already had them downloaded.
Now, where ever I used to have
Crashlytics.logException(e);
I'm getting an error similar to
The type io.fabric.sdk.android.Kit cannot be resolved. It is indirectly referenced from required .class files MonthlyOffer.java /JOM Android Phone App/src/joelosteen/android/phone/JOMApp/layout line 234 Java Problem
So are we not able to use logException with fabric?
** EDIT **
Thanks to sublime text 3 I did a find in files... and commented out every occorrence of lines with fabric or crashlytics in them:
find: (.*[fabric|crashlytics].*)
in: * (make sure this is your src folder)
replace: // $1
** EDIT **
Using Eclipse v4.2.0
I'm assuming you're using Android Studio. Are you using the latest version of Fabric (2.3.2 as of this writing)? Did the Fabric plugin add the necessary changes to your project?
You can log exceptions by using the logException method as outlined here
in trying to implement the answer to stage.stage3Ds is empty when debuging on Kindle Fire HD 8.9". I tried adding both renderMode and detailAndStencil to the application xml file but get this error when trying to debug to device.
Error occurred while packaging the application:
D:\Flash\Mobile Test\bin-debug\Main-app.xml(10): error 103: application.initialWindow.depthAndStencil is an unexpected element/attribute
The initialWindow portion of application xml file is below
<initialWindow>
<content>[This value will be overwritten by Flash Builder in the output app.xml]</content>
<renderMode>direct</renderMode>
<depthAndStencil>true</depthAndStencil>
</initialWindow>
It looks like depthAndStencil option is only available with AIR 3.2 onwards.
Looking through the template file that is used to generate the app descriptor file:
[AIR SDK ROOT]\templates\air\descriptor-template.xml
The entry for depthAndStencil first appears in the template file that comes with the AIR 3.2 SDK.
Edit:
Confirmed. See release notes for 3.2 SDK: http://helpx.adobe.com/flash-player/release-note/release-notes-developer-flash-player.html
I'm trying to update my iPad app on the App Store. I filled out the "new version" form on iTunes Connect and then tried to upload the new version with Application Loader. It rejected the .zip file giving me three errors.
I had changed the "Bundle Version" line in the Info.plist file to 1.1, and added "Bundle versions string, short" (also 1.1). Then I build the .app file, and zipped it up with the .mobileprovision file.
The zip file: Chordpad.zip
Contains: ChordPad.app, ChordPad_Distribution.mobileprovision
These are the errors Application Loader is giving me:
1. iPad: application executable contains unsupported architecture(s): i386
2. Application failed codesign verification. The signature was invalid, or it was not signed with an Apple submission certificate.
3. Unable to extract codesigning entitlements from your application. Please make sure ChordPad.app is a valid Mach executable that's properly codesigned.
As far as I know, all my certificates are valid. Could anyone please help me fix this?
If the i386 architecture is being used, you are probably building for the simulator. Switch to device to get the arm architectures.