Thursday, March 7th, 2013 11:17 am
(lldb) p [particle lifeVar]
error: cannot find interface declaration for '$__lldb_objc_class'
error: cannot find interface declaration for '$__lldb_objc_class'
error: 2 errors parsing expression
(lldb) p particle.lifeVar
error: warning: property access result unused - getters should not be used for side effects
error: cannot find interface declaration for '$__lldb_objc_class'
error: cannot find interface declaration for '$__lldb_objc_class'
error: 2 errors parsing expression
(lldb) p (CGFloat)[particle lifeVar]
error: warning: expression result unused
error: cannot find interface declaration for '$__lldb_objc_class'
error: cannot find interface declaration for '$__lldb_objc_class'
error: 2 errors parsing expression
(lldb) p (CGFloat)[(CCParticleSystemQuad*)particle lifeVar]
error: warning: expression result unused
error: cannot find interface declaration for '$__lldb_objc_class'
error: cannot find interface declaration for '$__lldb_objc_class'
error: 2 errors parsing expression
error: cannot find interface declaration for '$__lldb_objc_class'
error: cannot find interface declaration for '$__lldb_objc_class'
error: 2 errors parsing expression
(lldb) p particle.lifeVar
error: warning: property access result unused - getters should not be used for side effects
error: cannot find interface declaration for '$__lldb_objc_class'
error: cannot find interface declaration for '$__lldb_objc_class'
error: 2 errors parsing expression
(lldb) p (CGFloat)[particle lifeVar]
error: warning: expression result unused
error: cannot find interface declaration for '$__lldb_objc_class'
error: cannot find interface declaration for '$__lldb_objc_class'
error: 2 errors parsing expression
(lldb) p (CGFloat)[(CCParticleSystemQuad*)particle lifeVar]
error: warning: expression result unused
error: cannot find interface declaration for '$__lldb_objc_class'
error: cannot find interface declaration for '$__lldb_objc_class'
error: 2 errors parsing expression
Wednesday, September 5th, 2012 11:51 am
To add Keychain access group to your app you have to enable entitlements for this app in Xcode and add access group there. When you enable entitlements, Xcode automatically adds your bundle identifier to access group list. That's enough to use this string as shared access group in your app, right? WRONG. You get all kinds of error messages when trying to use shared access group, then open entitlements file and find that that access group is only displayed as nice and clean com.yourcompany.yourapp, and actually is $(AppIdentifierPrefix).com.yourcompany.yourapp. And when you remove this prefix, shared access group works all right. And after device&Xcode restart shared access groups without AppidentifierPrefix stop working, and start working with it.
Friday, July 13th, 2012 02:27 pm
Writing software for any kind of Apple devices is like playing croquet in Wonderland: flamingos twist, hedgehogs crawl away, soldiers walk off, and if you manage to get through all this, furious Queen is stamping about, shouting "Application rejected!"
Xcode is about as much useful as an IDE as flamingo is useful as a mallet or hedgehog as a ball. Bugs with autocomplete, scrolling, indexing of files; constant crashes - I had it crash on copying text, pasting text, opening a file, closing a file, saving a file, running project on device, clicking on error/warning marker, adding files to project, removing files from project, committing changes to repository... if I had no Xcode crashes in a day, it means that it was my day off.
Sometimes your code stops working, even you didn't change anything. One moment it works, next moment it doesn't. Sometimes removing project's derived data from Xcode, removing app from device, restarting Xcode and doing a clean build helps. Sometimes.
And then there are ~glitches~ like this one. Suddenly a mutable texture in my app was going greener and greener every time a pixel of it was set to (0, 0, 0, 0). Not only that, rendering that texture with glBlendFunc(GL_ZERO, GL_SRC_ALPHA) made destination texture more and more green and transparent, instead of cutting holes in it. I made a backup, reverted code to the last commit (even though I didn't make any changes in rendering code), and it worked okay. I added one of the changes from backup - and it worked okay. I added all the changes - and there were no glitches. Now I have two versions of the project, with identical code, one is glitching all over and other works like nothing happened at all.
Xcode is about as much useful as an IDE as flamingo is useful as a mallet or hedgehog as a ball. Bugs with autocomplete, scrolling, indexing of files; constant crashes - I had it crash on copying text, pasting text, opening a file, closing a file, saving a file, running project on device, clicking on error/warning marker, adding files to project, removing files from project, committing changes to repository... if I had no Xcode crashes in a day, it means that it was my day off.
Sometimes your code stops working, even you didn't change anything. One moment it works, next moment it doesn't. Sometimes removing project's derived data from Xcode, removing app from device, restarting Xcode and doing a clean build helps. Sometimes.
And then there are ~glitches~ like this one. Suddenly a mutable texture in my app was going greener and greener every time a pixel of it was set to (0, 0, 0, 0). Not only that, rendering that texture with glBlendFunc(GL_ZERO, GL_SRC_ALPHA) made destination texture more and more green and transparent, instead of cutting holes in it. I made a backup, reverted code to the last commit (even though I didn't make any changes in rendering code), and it worked okay. I added one of the changes from backup - and it worked okay. I added all the changes - and there were no glitches. Now I have two versions of the project, with identical code, one is glitching all over and other works like nothing happened at all.
Thursday, January 26th, 2012 04:05 pm
I added some new stuff to the code and suddenly the game began drawing platforms half a platform height above where platforms should be rendered. WTF? I did not change platforms code. Clean build did not help. Deleting derived data did not help.
So I cloned git of the project to another folder and started reverting to earlier versions. All versions were drawing platforms in wrong positions.
I switched back to latest version and ran it again. All platforms in their places. I ran it again. All platforms were above where they should be.
So I cloned git of the project to another folder and started reverting to earlier versions. All versions were drawing platforms in wrong positions.
I switched back to latest version and ran it again. All platforms in their places. I ran it again. All platforms were above where they should be.
Thursday, January 26th, 2012 12:43 pm
I need to subclass an abstract class. As I was implementing one of abstract class methods in my derived class, Xcode put a red error mark on "void Listener::BeginContact(b2Contact* c)" line, telling me there are three errors. I double checked my spelling and syntax and found no errors, so I clicked on error mark to see error descriptions. Xcode crashed.
When I restarted Xcode, error mark was still there. I clicked on it and Xcode crashed.
I restarted Xcode, deleted project's derived data, restarted Xcode again. Error mark was still there. I clicked on it and Xcode crashed.
I restarted Xcode, built the project (clean) - error mark was still there. I did the clean build again - and error mark was gone. W. T. F.
When I restarted Xcode, error mark was still there. I clicked on it and Xcode crashed.
I restarted Xcode, deleted project's derived data, restarted Xcode again. Error mark was still there. I clicked on it and Xcode crashed.
I restarted Xcode, built the project (clean) - error mark was still there. I did the clean build again - and error mark was gone. W. T. F.