I am using SDCAlertView
for custom alertview. It is perfectly working in ios 7 . But in ios8 alertview button are not visible . i am not able find actual problem .
Thanks in advance
I had absolutely same problem. So I've created test project to reproduce it. And I couldn't. It was working in small test program.
So I've just updated my project's pods. Just use pod update and rebuild your project. Most likely you have outdated version of SDCAlertView.
Related
Hi all am trying to achieve an autocomplete using nativescript for a project. It was working fine with nativescript-pro-ui, but i updated that plugin to nativescript-ui-autocomplete. Afterwards it begins to crash whenever i try to invoke that in ios, it works fine in android.Any help will be appreciated. Thanks
There are currently two open issues about a crash in iOS. I see this is an old issue and they are probably not related to this one but I'm listing them here for reference.
https://github.com/NativeScript/NativeScript/issues/9031
https://github.com/ProgressNS/nativescript-ui-feedback/issues/1487
I have just changed my app from supporting iOS 8 and up to supporting iOS 9 and up. I believe I've done this properly, since when I now build my app, I'm getting warnings for everything in the app which was deprecated in iOS 9.
I am using Xcode 9, GM seed.
The problem is that I cannot enable the "Use Safe Area Layout Guides" toggle in any of my storyboards. When I do, I get a warning "Safe Area Layout Guide before iOS 9.0". Is there some additional setting that I need to update? A clean and build did not fix the problem.
Just deselect "Use Safe Area Layout Guides" option, which should fix this.
A screenshot below may point you the right direction.
Hope this image can help
When you changed the deployment target, did it automatically change the deployment target in your storyboard? (File inspector when opening the Storyboard)
Did you update the deployment target in both the Project and in (all) your target(s)?
Project:
Target:
I didn't try quitting Xcode and restarting it before posting to SO! Sorry! The answer is, quit Xcode and try again.
Simple fix.
In file inspector for the view, look for Builds For in Interface Builder Document and in there select iOS 9 and later.
What are illegal configurations and how do I fix them?
I have 3:
Launch screens may not use instances of IBUIExitPlace Holder.
Launch screens may only have one top level object, which must be a UIView or a kind of UIViewController.
Launch screens may not use instances of IBUIStoryboardEntryPointIndicator.
I'm converting my Swift 2 code to Swift 1.2 so I can upload my app to the app store.
Thanks in advance!
I just stomped with the exact same issue.
I think you can reproduce the issue with the following steps:
Create a Launch Screen.storyboard using Xcode 7 beta 5
Open Xcode 6.4 and try to build the project, it should fail.
What I did to fix this was to delete the Launch Screen.storyboard created on XCode 7b5 and create a new one on XCode 6.4.
Please let me know if you try this solution!
Encountered the same issue. This issue is generally caused because of creating a Storyboard using XCode 7 and using the same Storyboard file in Xcode 6. Follow the below steps to solve the issue.
Delete the LaunchScreen storyboard created by Xcode 7.
Create a new LaunchScreen storyboard using Xcode 6.
Clean and Build.
I know there are several issues with the new version of xcode 5.1/cordova and it simply wont run apps on 64x bit devices / emu but I followed this tutorial and now it somehow works (even though it spits 14 warnings in my case)
But for some reasons config.xml is still being ignored. It's in red and you can't edit it.
Any suggestions?
You need to close your xcode. Build again using cordova build and open up again your xcode then you can run your app.
Just upgraded from Xcode 3 to Xcode 4 and built my app, but all I see is a white window. If I minimize the app and open up the app again everything looks good.
I have also tried to just add a simple UIImageView to the window in my appdelegate but I get the same behavior.
I have also tested to just create a new test project and it works as it should.
Any ideas?
I am not exactly sure what the problem could be... but since you say that a new test project works perfectly, the thing I can think of is that you might need to change build/ target settings in ur project by editing your scheme.. try that out...