I downloaded iOS7 GM earlier and an the following error appeared when building on simulator and/or device:
Terminating app due to uncaught exception 'NameError', reason: 'uninitialized constant BubbleWrap::Device::Camera::KUTTypeMovie (NameError).
What's strange is that I only require bubble-wrap/core in my Rakefile. Also the only functions I use from bubblewrap are BW::JSON and App.Persistence.
If I change the xcode-select path back to xcode4, the app runs again.
Any ideas?
P.S. I have the latest rubymotion and (I think) the latest BubbleWrap (since in the Gemfile, I have the following line, but I'm new to rubymotion/ruby:
gem 'bubble-wrap', :git => 'https://github.com/rubymotion/BubbleWrap.git'
Edit: Also tried requiring bubble-wrap/camera (even if I don't use the camera), updating xcode command line tool.
Seems I was a little bit to hasty. From #rubymotion on Twitter, GM is not supported yet but should be really soon. Meanwhile, a user on the rubymotion google groups post a monkey patch
Related
I upgraded to react-native 0.16.0-rc, ran npm install, then ran react-native upgrade. When trying to launch the iOS app in a simulator (or device, doesn't matter) I get the error:
[error][tid:com.facebook.React.RCTExceptionsManagerQueue] Unhandled JS Exception: babelHelpers.interopRequireDefault is not a function. (In 'babelHelpers.interopRequireDefault(_reactNative)', 'babelHelpers.interopRequireDefault' is undefined)
I've just about run out of ideas here. Is there something I need to add to my xcode project maybe? Merging the latest react-native templates into mine was a nightmare so maybe something got messed up there.
This problem is discussed in this Github issue and fixed by this commit. You can apply this patch temporarily until it is merged into the project with the version 0.16.
I'm trying to submit a WatchKit app to the App Store but get this error.
Another cause for this is including a WatchKit or any other TargetApplication.app inside your application bundle.
Do not include any in your project settings > target > Build Phases > Copy Bundle Resources.
A bug in Xcode (6.2..) added it there when I tried to add it to Target > General > Embedded Binaries. Nothing changed in that section and no errors were shown so I ignored the bad feeling it gave me.
After hours dealing with other certificate issues (and hosing all of our TestFlight testers, due to revoking distribution certs, which was apparently/probably required), upgrading to Xcode 6.3.1 I finally remembered this bad feeling and found the app watchkit application lurking in the Copy Bundle Resources section and removed it.
In addition to the Invalid Bundle Structure error above the specific errors exhibited for me were:
ERROR ITMS-90378: "CFBundleIdentifier Collision. There is more than one bundle with the CFBundleIdentifier value 'com.company.App.watchkitapp' under the iOS application 'App.app'
ERROR ITMS-90451: "CFBundleIdentifier Collision. The Info.plist CFBundleIdentifier value 'com.company.App.watckitapp' of 'App.app/App Watchkit App.app' is in conflict with the Info.plist CFBundleIdentifier value of 'App.app/Plugins/App Watchkit Extension.appex/App WatchKit App.app'
All were gone and submission worked fine after removing.
Also, validation passed fine even with both instances of the watckit app.
You cannot submit WatchKit apps yet even though Xcode 6.2 and iOS 8.2 are officially out. See the following answer for more info.
All of a sudden, and through no apparent changes on my end, I am now getting the following error from an image in my asset catalog:
2013-10-30 14:44:46.629 MyApp[38590:a0b] CUICatalog: Can't find rendition for name: LoginBackground scale factor: 2 device idiom: 1 device subtype: 0
2013-10-30 14:44:46.638 MyApp[38590:a0b] Could not load the "LoginBackground" image referenced from a nib in the bundle with identifier "com.mybundleid"
I have tried removing the image assets and re-adding them, to no avail. The issue is happening in the simulators as well as devices. And oddly enough I can still see the image in the storyboard. Adding the images directly to the project worked as well.
Has anyone else ever seen this error? What's going on?
Update: CocoaPods 0.28.0 appears to have resolved this issue.
Are you using CocoaPods to manage your dependencies? It's possible a recent update has caused this.
I encountered the same issue with a universal app recently. Image sets that included separate, device-specific resources only included assets for a single device type after build. I similarly had made no apparent changes to the project around these assets and my storyboards appeared correct.
After Googling around, I discovered issues with Asset Catalogs reported on the main CocoaPods project (https://github.com/CocoaPods/CocoaPods/issues/1520) and realised that perhaps updating CocoaPods could be the change that wasn't apparent.
Rolling back my installation of CocoaPods from 0.27.1 to 0.26.2, the release before support was included for compiling xcassets in Pod dependencies, appears to have fixed this issue for now. I'll be keeping an eye on upcoming releases as it seems there is very active development in this area.
I downgraded cocoapods to 0.26.2 and it fixed the issue for me.
I'm working with Alex Reisner's geocoder gem on a Rails 3 app (3.0.3) because I'm concerned about GeoKit's shakey Rails 3 compatibility. Alex's gem looked perfect for my application so I started using it and had it working flawlessly last night on my Macbook. I pushed the app to Github when I got it running.
Today, I did a git clone of the app on a desktop Mac. Same version of Ruby, Rails and identical source and Gemfile. This time geocoder is throwing this exception:
NameError (uninitialized constant Geocoder::Net):
app/controllers/restaurants_controller.rb:16:in `create'
My models use after_validation :fetch_coordinates to geocode the model upon save.
Has anyone noticed any other dependencies outside the bundle that could cause this? I like the way Alex put this one together but may give geokit-rails3 a try even though it's an unfinished port.
I just released gem version 0.9.7 which should solve this problem.
I had upgraded my OS into Snow Leopard, and I'm using Xcode 3.2 with iPhone SDK 3.0 for Snow Leopard.
I had cleaned up the existing Developer Tools, uninstall, and I deleted the /Developer directory, and I reinstall.
But, the problem is, Interface Builder is showing 3 pop up alerts with this message:
Assertion Message: Interface Builder encountered an error communicating with the iPhone Simulator. If you choose to file a crash report or radar for this issue, please check Console.app for crash reports for "Interface Builder Cocoa Touch Tool" and include their content in your crash report.
IBUIViewImageRequester failed to rasterize a UILabel, UIButton, UITextField, and UISegmentedControl.
Exception name: NSInvalidSendPortException
Exception reason: [NSMachPort sendBeforeDate:] destination port invalid
Exception backtrace:
(null)
Exception info:(null)
Some people had experienced this, and some people were able to resolve it by copying the right IBCocoaTouchPlugin.ibplugin from those not experiencing problems.
So if anybody could share it, that would be great.
I could click continue to proceed, but it's an annoying problem.
Update:
It's caused by IB that's linking to the wrong libstdc++ in /usr/local/lib. The IB should link to libstdc++ in /usr/lib/
Just delete or move the interfering libs.
It's caused by IB that's linking to the wrong libstdc++ in /usr/local/lib.
The IB should link to libstdc++ in /usr/lib/
Just delete or move the interfering libs.
I had the same problem. I moved the /usr/local to another place, and the problem was solved.
Update: I ran into a very similar problem today. The solution was to delete my old /Developer folder I used with Xcode prior to 4.0.