Sunday, June 19, 2016

Your binary is not optimized for iPhone 5



If you get the folowing:

Do as per pictures:



to solve the following issue.




ERROR ITMS-90096: "Your binary is not optimized for iPhone 5 - New iPhone apps and app updates submitted must support the 4-inch display on iPhone 5 and must include a launch image referenced in the Info.plist under UILaunchImages with a UILaunchImageSize value set to {320, 568}. Launch images must be PNG files and located at the top-level of your bundle, or provided within each .lproj folder if you localize your launch images. Learn more about iPhone 5 support and app launch images by reviewing the 'iOS Human Interface Guidelines' at 'https://developer.apple.com/library/ios/documentation/UserExperience/Conceptual/MobileHIG/IconsImages/IconsImages.html#//apple_ref/doc/uid/TP40006556-CH14-SW5' and the 'iOS App Programming Guide' at 'https://developer.apple.com/library/ios/documentation/iPhone/Conceptual/iPhoneOSProgrammingGuide/App-RelatedResources/App-RelatedResources.html#//apple_ref/doc/uid/TP40007072-CH6-SW12'."
ERROR ITMS-90096: "Your binary is not optimized for iPhone 5 - New iPhone apps and app updates submitted must support the 4-inch display on iPhone 5 and must include a launch image referenced in the Info.plist under UILaunchImages with a UILaunchImageSize value set to {320, 568}. Launch images must be PNG files and located at the top-level of your bundle, or provided within each .lproj folder if you localize your launch images. Learn more about iPhone 5 support and app launch images by reviewing the 'iOS Human Interface Guidelines' at 'https://developer.apple.com/library/ios/documentation/UserExperience/Conceptual/MobileHIG/IconsImages/IconsImages.html#//apple_ref/doc/uid/TP40006556-CH14-SW5' and the 'iOS App Programming Guide' at 'https://developer.apple.com/library/ios/documentation/iPhone/Conceptual/iPhoneOSProgrammingGuide/App-RelatedResources/App-RelatedResources.html#//apple_ref/doc/uid/TP40007072-CH6-SW12'."

Saturday, June 18, 2016

Nativescript {N} - build-tools/22.0.1/aapt failed with Nativescript android


If you get the following:

Error:Execution failed for task ':processNativescript-barcodescannerNativescript-telerik-uiDebugResources'.
> com.android.ide.common.process.ProcessException: org.gradle.process.internal.ExecException: Process 'command '/Users/.../Library/Android/sdk/build-tools/22.0.1/aapt'' finished with non-zero exit value 2


Go to your build.gradle for your app and change from:

def computeBuildToolsVersion() {
   if(project.hasProperty("buildToolsVersion")) {
      return buildToolsVersion
   }
   else {
      return "22.0.1"   }
}

to

def computeBuildToolsVersion() {
   if(project.hasProperty("buildToolsVersion")) {
      return buildToolsVersion
   }
   else {
      return "23.0.1"   }
}

 You must install SDK buikd tool for 23.0.1 to get it work. NativeScrupt has a bug that does not work with SDK 22.0.1.

Saturday, April 30, 2016

Androids useful debugging information



Android: Refusing to read from unsafe file location
--------------------------------------------------------------
If you have files in other paths than  /mnt/sdcard
this is considered to be unsafe and Android will refuse to read it no matter if this is a video file in mp4, images in jpeg, jpg.

Have your files in /mnt/sdcard to read from .




Tuesday, February 2, 2016

Running Docker-machin in another location than C:/Users



In order to run docker-machine to other location than default, use the -s option or --stiorage-path as follows:

$docker-machine -s /f/.docker/machine/machines/ create --driver=virtualbox dev

However later docker runs will still point to default path, so in order to get the env to the new docker-machine you ahve to run the followinG:

$docker-machine -s /f/.docker/machine/machines/  env dev

To change default pathway to docker use :
MACHINE_STORAGE_PATH=/f/.docker/machine/machines/

You can add this in your start.sh or ~/.bashrc or in windows env variable to use the other location.




Tuesday, August 25, 2015

Ignore changes in tracked files using GIT





Use:
git update-index --assume-unchanged <file>

To ignore changes in tracked files.


Use:
git update-index --no-assume-unchanged <file>

If you want to check in changes in those tracked files.



Wednesday, May 6, 2015

Rename VM to another name



In the command line run the followinG:

$vboxmanage modifyvm ORIGNAL_NAME --name NEW_NAME

Tuesday, April 28, 2015

Setting up boot2docker and working with live-reload directory the easy way



Checkout https://github.com/boot2docker/boot2docker/pull/534

Download latest boot2docker from:
https://github.com/boot2docker/windows-installer/releases

If you access the boot2docker VM via the following:
$boot2docker ssh

You will not be able to have access to your host developement files. To make your
developement files accessible do the following in Windows:

$boot2docker stop
$VBoxManage.exe sharedfolder add boot2docker-vm --name Users --hostpath C:/Users --automount.



Note 1: if you are using cygwin you have to use the syntax C:/Users, not C:\Users
Note 2:
hostpath Users` share at `/Users` in the boot2docker VM
hostpath /Users` share at `/Users`  in the boot2docker VM
hostpath c/Users` share at `/c/Users`  in the boot2docker VM
hostpath /c/Users` share at `/c/Users`  in the boot2docker VM
hostpath c:/Users` share at `/c/Users`  in the boot2docker VM


$boot2docker up
$boot2docker ssh "ls /Users"

Voila!  You will see your files inside boot2docker !

But how about using another path than Users above ?
Do as follows:


$VBoxManage.exe sharedfolder add boot2docker-vm --name Afrepo --hostpath F:/gitrepositories2 --automount

$ boot2docker ssh "ls /"
You will not find your Afrepo in the list, right? Try the following:
$ boot2docker ssh "mkdir /home/docker/Afrepo && sudo mount -t vboxsf -o uid=1000,gid=50 Afrepo /home/docker/Afrepo"


You files at F:/gitrepositories2 - in your host will be accessible inside boot2docker VM and finally to your docker !

Try the following:
$ boot2docker ssh
$docker run -v /Users/...:...   if you have used Users as sharename or
$docker run -v /Afrepo/...: ...  if you have used Afrepo as sharename