While it was definitely a mistake to not check that the file name matched the image call in the app–it wasn’t made easier to find this problem since the simulator happily displayed the image “properly”.

Sigh, a new version of the affected app has been submitted, but i really wonder why these types of glitches in the dev tools happen.

ShareThis

I’m still working on the theme elements, but for those of you having the major slowdown issue this version will fix that while you wait for the next full release.

The files can be downloaded here: http://www.awsom.org/filerepository/awsom-pixgallery460beta1.zip. Just replace the files on your server with these and you should be good. Load the settings page and save the options to enable the new setting.

ShareThis

Advertisement: Check Out My Online Store

ShareThis

I’ll put up the new version as soon as I can confirm that nothing else goes boom when the fix code is active.

ShareThis

Well, in short, the rename function was failing. After trying to do a rename Xcode would crash with an error– Internal error NSCFArray insertObject:atindex attempt to insert nil .

Yeah, not very helpful. The error seems to imply that something somewhere is being renamed but with nothing to input, or with something that’s nil already. So now I’m paranoid about our app. Did we make a mistake somewhere? Is there a cul-de-sac area of the program that doesn’t cause it to crash but is now showing an error when renamed? UGH!

I tried everything I could to find the issue, but it eluded me.

Then it struck me. Did any other apps rename properly? NOPE!

The rename function itself seemed screwed up. So I reinstalled Xcode. It still didn’t work!

What the hell? What do I do now? Then I started thinking. What’s the most basic thing that can go wrong in OS X? Yes, permissions issues.

So I moved the app out of the default applications folder in Xcode and moved it to the desktop. Guess what…it now worked to rename it!

All I can think is that at some point down the line something got screwed up with the permissions for the Xcode folders. It looks like a file with the xproj folder called foo.pbxuser didn’t have permissions to be rewritten with the renaming. So it failed.

Oh, BTW, when the rename failed it deleted the original xproj file for the app….so again with all things, always make a backup of your files before trying to do anything like this.

Anyway, I hope this helps anyone else who might have this issue.

ShareThis

The first difficult part of the iPhone app store is getting your actual sign up approved. If you go to developer.apple.com you can start the process for signing up for your account. The one good thing about this is you can choose to go the “easy” route at first and only sign up for unpaid app (i.e. free apps) development. While this route is a bit easier, it still costs you some cash–$99 per year. Yes, you have to pay to develop apps that will make you no money from the store (of course, you can make money through other things other than purchases of the app).

One of the big pitfalls of this system is really the paid app sign up. This requires you to get a ton of financial info together and fax it off to Apple. (they want bank account and address info). Here’s where some major problems can crop up–You can’t easily change the data once they receive it. As part of your sign up you need to fill out some online forms with your company name and other info (tax, address, financial). If you make a mistake on some of these, you’re in trouble. There is no way to have this changed through the online interface. In fact, there’s no clear way to actually contact them over this.

We had an issue with our address. It looks like someone at Apple actually types in your info from the faxed forms you send over–and they did it wrong for us. What you end up with is a screen that shows you your info, but no clear location to contact Apple to correct it. I literally sent a customer contact email through every CSR interface on the Apple site and got no reply. About 2 months later I received an email from a CSR saying basically “Fax us a new copy of your company incorporation document” with the statement that they would then go in and make the necessary edits.

Look, 2 months is not a reasonable time frame for this type of thing. What if the issue had been with our financial info instead of something minor?

So, the main point of this is really think about what you will be entering into their sign up forms. As far as I can tell, you can’t make many changes later. (As a side note–there are reports that this is really a problem in other areas. It seems like it’s impossible to take over software from another account. For instance, if you were to buy another iPhone developer’s software business there isn’t a real way to combine accounts or move the apps without literally resubmitting them and losing any history or linkage.)

While Apple does a good job with their customer facing interface. Expect many hassles and surprising lapses with their business interfaces. This is just the beginning though, just wait until you here about the dev interfaces in the next posts.

ShareThis

In many ways I see the iPhone service as similar to why I started this site. It’s not easy doing coding. Creators mostly don’t have time to even begin to look at this stuff. It’s also very hard and a very specialized skill, so it’s not something that many can even do. So once again we’ve stepped in to help in an area that we can provide our skill to the community.

So I plan on outlining some of the things we’ve discovered while developing our apps in hopes that it will make it easier for others to do so, and also outline why we decided to do the service in the first place (in other words, why it’s such a bitch to get anything developed for the iPhone).

So, the tales will soon begin. Brace yourself, it’s a bumpy ride.

ShareThis

Now if only I can get them to see the power of the AWSOM set of plugins life would be perfect. And yes guys, I’ll consider trading some work for some free park tickets :)

Advertisement: Check Out My Online Store

ShareThis

Of course you will now always need to remember to either add this back in after upgrading versions of WordPress, or keep a copy of this file and just merge it into things afterward (and make sure any updates didn’t affect this file).

The one thing that is unfortunate is I was hoping to be able to add some stuff to my plugins for this for anyone to benefit, but can’t. Oh well.

ShareThis

The actual code to get separate loops working is a bit tricky, but not too hard once you understand the process. The major issue arose in getting both posts to appear and not overlap or conflict when appearing side by side.

The typical way to do this in a theme is to make both loops into separate HTML div’s, then do a float on them to get them to appear next to each other. The problem comes in when you need to retrofit this into a theme and CSS setup that wasn’t initially set up with this expectation.

The cascading nature of CSS is normally a good thing–the evil comes in due to different web browser compatibility levels, as well as weird “by design” issues with CSS itself. One of the most frustrating things with CSS is that due to the cascade, you may not actually easily know why something isn’t appearing correctly. While the element level can clearly have a specific CSS entry that tells it to do something, there are times when an overarching CSS entry (like a div level img setting behavior) can override your local entry. It involves which CSS entry the browser decides to do first, then second. You would assume that the local entry would trump the div level one, but that’s not always the case.

Anyway, back to my specific problem: The floats for the 2 news entries weren’t working properly. The CSS caused elements from both div’s to overlap, or get pushed under the other div. Or the background wasn’t being extended correctly behind both divs. It was turning into a mess.

Then the answer hit me: screw CSS for placement. While I’m sure many people will choke on this statement: Tables almost always work properly for placement, so use them sometimes where appropriate. In my case all I needed to do was make a simply 2 row table and place each loop inside each td.

Boom, works great and no issues for any browsers. And yes, I did use CSS to make the look of the table correct. A bonus is the mobile version of the site looks perfect since tables are easy things to get correct in even the crappiest mobile browser.

So, my lesson is sometimes it’s not worth ripping things apart when the simple solution is available.

Advertisement: Check Out My Online Store

ShareThis