How do you hide the status bar on the splash/launch screen (titanium) - titanium-mobile

<fullscreen>true</fullscreen>
<navbar-hidden>true</navbar-hidden>
I have tried this (in the tiapp.xml) settings, but it doesn't work.
Any idea how to resolve this problem.

Seems like Titanium has changed things:
<key>UIStatusBarHidden</key>
<true/>
Set that to true in your tiapp settings

Related

Background Mode doesn't be added in Xcode

I want to add Background Mode to use Location Updates but I can't.
I already know the place of Background Mode but I don't know why it doesn't work.
https://drive.google.com/file/d/1A7CeRiios1vD51u3OmM1qTAs7AxVVmE6/view?usp=sharing
I recorded the situation so you can see it in that link.
I solved the problem by adding
<key>UIBackgroundModes</key>
<array>
<string>location</string>
</array>
this code to Info.plist.

isFullScreen manifest setting doesn't do anything

I've created a simple Teams app with a single Personal tab defined.
In the manifest there is a setting isFullScreen: true. My hope was that enabling this property would no longer show the Tabs bar on top of the application. However, this does not seem to be the case.
Furthermore, I don't see any change in the application, whether isFullScreen is set to true or false.
Does anyone know what this property actually changes? Or am I missing something else perhaps?
This is a known issue. We have raised a bug for this and we are working on fixing this. But we cannot give you an ETA on when this will be available.
I checked this morning, and the issue is resolved.
The isFullScreen flag now works as expected.

Xcode ERROR ITMS-90783: "Missing bundle display name"

Today I started to receive this error with fastlane and Xcode:
ERROR ITMS-90783: "Missing bundle display name. The Info.plist key
CFBundleDisplayName is missing or has an empty value in the bundle
with bundle identifier 'com.id'."
It was ok and I didn't remove this property. I think this is a bug on Apple's side.
Does anyone have the same issue and how did you fix it?
Just add a new property to info.plist:
<key>CFBundleDisplayName</key>
<string>$(PRODUCT_NAME)</string>
Open "info.plist" from your project folder.
And add key:"Bundle display name" or CFBundleName
and write value:"your app name". or add product name like this $(PRODUCT_NAME)
Key value example
<key>CFBundleName</key>
<string>$(PRODUCT_NAME)</string>
Then your problem will be solved!
In Xcode, you could add "Display Name" by following the illustration below.
I am having the problem too. Although a newly project has this in its info.plist:
<key>CFBundleName</key>
<string>$(PRODUCT_NAME)</string>
That broke in the last few days for me. Now I hard code CFBundleName to the application name and that seems to work.
Just go to the Info.plist and check if there is an entry for CFBundleDisplayName
If it is not there then : Open source code of your Info.plist and add this
<key>CFBundleDisplayName</key>
<string>$(PRODUCT_NAME)</string>
Now try archiving, you will succeed this time.
This is a new requirement introduced 5-7 days back.
Cheers!!
I was going through the answers here and when I checked my file it looked to be what it supposed to be, I had not touched the info.plist file in days. Then I noticed something, instead of $(PRODUCT_NAME) I had ${PRODUCT_NAME). Weirdly there was a curly bracket. Since I'm using 2 info.plist files for different targets, I decided to check if the other one also contains the curly bracket and it did.
I'm getting this error, too. Wasn't happening a week ago. I tried entering in a bundle name in the Bundle Identifier but that didn't work. Had to actually paste in $(PROJECT.ROOT) in the Bundle Identifier item of the info.plist, re-archive and then upload to the app store.
If that doesn't work, there's another possible solution. It appears that Apple may be requiring the plist entry "Bundle name" to be added with a value of $(PRODUCT_NAME). If you don't have that in your info.plist, you will need to add it, then try again.

Xcode: indent code in a single shortcut

I'm using Xcode 7.3 with Swift 2.2.
The point is that I'm largely tired of "running":
Cmd + A
Ctrl + I
in order to indent the whole code.
So, I think I'm quite close to find the solution, creating my own shortcut on IDETextKeyBindingSet.plist.
<key>My Custom Shortcuts</key>
<dict>
<key>Indent Code In One Hit</key>
<string>selectAll:, ....., moveLeft:</string>
</dict>
I have done a lot of test substituting '.....' with various commands (combining this), but I can't find a solution yet.
Any help is appreciated!
Finally I found a solution by my self, without installing any unverified plugins.
I think that could be other solutions with higher performance.
Close Xcode
Edit IDETextKeyBindingSet
sudo nano /Applications/Xcode.app/Contents/Frameworks/IDEKit.framework/Resources/IDETextKeyBindingSet.plist
Adding this:
<key>My Custom Shortcuts</key>
<dict>
<key>Custom - Indent Code In One Hit</key>
<string>selectAll:, cut:, paste:</string>
</dict>
Open Xcode, Cmd + ; to open preferences
Key Bindings and filter by "Custom"
Assign you favourite key binding.
Exit from preferences, stir your code, try your new shortcut and feel the power!
I think you should try this. It helps you re-indent code each time you Cmd + S
"Command + ]" will indent all the highlighted code.

_BSMachError XCode 7 Beta

I am getting the following error when I am running my code in Xcode7 with Swift2, after presenting a view controller through a push segue:
_BSMachError: (os/kern) invalid capability (20)
_BSMachError: (os/kern) invalid name (15)
The other SO articles had no resolution, does anyone know about this issue?
Although this problem seems to persist as a bug and will likely be fixed, it stems from the new App Transport Security that has been implemented in iOS 9.
If your application pulls data from a web server, in order to populate the View Controller that you will be presenting, you can resolve these errors by verifying/granting access to the particular site(s) you're pulling from.
In order to address this you will add the following to your App's .plist file:
You may want to alter your ATS Exception Dictionary to fit your needs
<key>NSAppTransportSecurity</key>
<dict>
<key>NSExceptionDomains</key>
<dict>
<key>testdomain.com</key>
<dict>
<key>NSIncludesSubdomains</key>
<false/>
<key>NSExceptionAllowsInsecureHTTPLoads</key>
<false/>
<key>NSExceptionRequiresForwardSecrecy</key>
<true/>
<key>NSExceptionMinimumTLSVersion</key>
<string>TLSv1.2</string>
<key>NSThirdPartyExceptionAllowsInsecureHTTPLoads</key>
<false/>
<key>NSThirdPartyExceptionRequiresForwardSecrecy</key>
<true/>
<key>NSThirdPartyExceptionMinimumTLSVersion</key>
<string>TLSv1.2</string>
<key>NSRequiresCertificateTransparency</key>
<false/>
</dict>
</dict>
</dict>
More details to this solution can be found here or here
The Apple Documentation for App Transport Security is worth reading too.
I had the same two error messages. In my case, the errors were appearing when I called [[UIApplication sharedApplication] openURL:url] after the user selected a button in an open UIAlertController. I assumed the alert was trying to close at the same time I was trying to open the URL. So, I introduced a slight delay and the error message went away.
dispatch_after(0.2, dispatch_get_main_queue(), ^{
[[UIApplication sharedApplication] openURL:url];
});
Not sure if this helps with your particular problem, but I thought it might be helpful to share.
Change the Localization native development region key in your info.plist from en to United States
Dismissing view controller prematurely might cause this.
[self dismissViewControllerAnimated:YES completion:NULL];
//<do something..>
This throws _BSMachErrors
vs
//<do something..>
[self dismissViewControllerAnimated:YES completion:NULL];
Now, the _BSMachError is gone.
I got these errors when I was using the keyboard. According to this note in Apple Docs, this is somewhat expected.
http://cocoadocs.org/docsets/Keyboard/0.3.0/
I make like that
dispatch_async(dispatch_get_global_queue(DISPATCH_QUEUE_PRIORITY_DEFAULT, 0)) { () -> Void in
AnswersDataServerEntity.saveSingleDocoment(doc)
}
Having this statement right below IBAction Button was causing the issue.
self.view.endEditing(true)
The issue was fixed in Swift 3, by commenting out the above line and handling the end editing in a different way, or can also be fixed adding the above line after all other code under IBAction.
I had this problem while debugging and it disappeared when I removed a breakpoint in my response to the view size changing.

Resources