ios - Xcode 6.3: Could not load NIB in bundle -


when compiled using xcode 6.3 (ios 8.3 sdk), nib filenames end ~ipad or ~iphone in circumstances. example, viewcontroller~ipad.xib becomes viewcontroller~ipad~ipad.nib. causing crash because app doesn't expect compiled nib files have double suffix.

to fix this, uncheck “use size classes” in affected documents in interface builder.

this appears bug in version of ibtool included xcode 6.3 (and ios 8.3 sdk). it's happening in following circumstances:

  • you have device-specific input file *~(iphone|ipad).xib size classes enabled.
  • your deployment target older ios 8.0.

i able reproduce problem on command line:

xcrun --sdk iphonesimulator8.3 ibtool --minimum-deployment-target 7.0 --compile viewcontroller~ipad.nib viewcontroller~ipad.xib

if you're seeing same behavior, please duplicate this radar. appears fixed in latest xcode 6.4 beta.


-

Popular posts from this blog

debugging - Reference - What does this error mean in PHP? -

what this? this number of answers warnings, errors , notices might encounter while programming php , have no clue how fix. community wiki, invited participate in adding , maintaining list. why this? questions "headers sent" or "calling member of non-object" pop on stack overflow. root cause of questions same. answers questions typically repeat them , show op line change in his/her particular case. these answers not add value site because apply op's particular code. other users having same error can not read solution out of because localized. sad, because once understood root cause, fixing error trivial. hence, list tries explain solution in general way apply. what should here? if question has been marked duplicate of this, please find error message below , apply fix code. answers contain further links investigate in case shouldn't clear general answer alone. if want contribute, please add "favorite" error message, warning or notic...
Read more

c++ - Why doesn't unordered_set provide an array access operator -

i'm curious why stl container unordered_set , has constant time complexity random access on average, not provide method accessing elements distance first element in container. example: t& unordered_set::operator[](size_t index) { return *(begin() + index); } accessing element "by distance" implies there meaningful way measure distance. trouble std::unordered_set is is, well, unordered . hence, there no meaningful way of explaining "some distance beginning" in non-arbitrary way. if want access distance, copy data vector: std::vector tmp(unordered.begin(), unordered.end());
Read more