iOS Help needed in solving this mess.

[troop231]

Congratulations!

I'll try to remember to check it out. I'm on the road for a few days and starting a new job, so I'll be pretty busy for the next week or three.

I had to reject the binary, I found a nasty bug I can't figure out, it's so nasty that you have to delete the app on the device/simulator to get it to work again.

I setup a url shortener on my server, that way the links in the app's plist aren't hard coded, and this will allow me to change redirects to a different server without submitting an app update.

The url shortener just redirects traffic. It works perfectly on all urls, except my pdf file's url, and when I change the redirect url on my server, the changes won't take effect until you delete the app and reinstall. Example: shorturl.com/pdf redirects to url.com/file.pdf and that works fine, but if I change it to redirect to url.com/filetwo.pdf it still loads the url.com/file.pdf This is not good! It sounds as if something is being retained through the app's lifecycle, but I don't see how.

What I don't understand is my other dynamic (redirect urls) work fine, and the changes on the server are reflected immediatelyin the app. (I use one of these urls to check to see if a server is online.)

Do you think you could help me fix this bug?

 

[xStep]

What I don't understand is my other dynamic (redirect urls) work fine, and the changes on the server are reflected immediatelyin the app. (I use one of these urls to check to see if a server is online.)

Do you think you could help me fix this bug?

It may be something that you have to follow through with the debugger and/or some NSLog statements. Search your code to see where the variable is used and assigned to.

Unfortunately I can't commit to helping. I start a new iOS job Monday and I'm currently driving 1800 miles to get there. I have 1400 to go, and hope to visit Mount Rushmore on the way!

----------

I also think I have thought of one consideration. What will users do when they next update and find they don't have their documents because the update doesn't come with them?

An idea might be to post an update that keeps track of what documents they look at. Immediately upon startup of the 'new' non-preloaded document version, let the user know that they need to download those tracked documents.

I'm glad you also mentioned this problem. I can imagine users being surprised at an in-opportune time.

 

[troop231]

It may be something that you have to follow through with the debugger and/or some NSLog statements. Search your code to see where the variable is used and assigned to.

Unfortunately I can't commit to helping. I start a new iOS job Monday and I'm currently driving 1800 miles to get there. I have 1400 to go, and hope to visit Mount Rushmore on the way!

I solved it! I had to change this line:

NSURLRequestUseProtocolCachePolicy

to this line:

NSURLRequestReloadIgnoringLocalAndRemoteCacheData

Cannot believe something as simple as that required the app to be deleted :O

Have fun on your trip by the way!

 

[dejo]

Unfortunately I can't commit to helping. I start a new iOS job Monday and I'm currently driving 1800 miles to get there. I have 1400 to go, and hope to visit Mount Rushmore on the way!

Congratulations on the new job! Care to spill any beans about it? And don't forget to stop by The Devils Tower, since you'll kinda be in the area!

 

[xStep]

Congratulations on the new job! Care to spill any beans about it? And don't forget to stop by The Devils Tower, since you'll kinda be in the area!

Thanks for the attraction tip. I hadn't a clue where that was.

I'm working for a large consultancy group who has a contract for porting/creating medical related software to the iPad. The location is Minneapolis MN.

 

[troop231]

Thanks for the attraction tip. I hadn't a clue where that was.

I'm working for a large consultancy group who has a contract for porting/creating medical related software to the iPad. The location is Minneapolis MN.

Yes, congrats on your new job!

By the way, I worked up an even lighter way to check for updates, before, I was checking a 233 byte plist file, but even then I was not pleased, so I'm now comparing two .txt files strings, and each .txt file is only 8 bits (1 byte) lol this will save on bandwidth more too I tested this many times by editing the .txt integer by adding +1 to the current, and sure enough it said update available, score!

        NSString *documentsDirectory = [NSSearchPathForDirectoriesInDomains(NSDocumentDirectory, NSUserDomainMask, YES) objectAtIndex:0];
        NSString *path = [documentsDirectory stringByAppendingPathComponent:url4];
        
        
        NSString *server = [NSString stringWithContentsOfURL:[NSURL URLWithString:url5] encoding:NSASCIIStringEncoding error:nil];
        NSString *local = [NSString stringWithContentsOfFile:path encoding:NSASCIIStringEncoding error:nil];
        
        
        if ( ![local isEqualToString:server] ) { UIAlertView *alertView3 = [[UIAlertView alloc] initWithTitle:@"Update Available!" message:@"Would you like to download the new regulations?"  delegate:self cancelButtonTitle:@"Cancel" otherButtonTitles:@"OK",nil];
            [alertView3 show]; alertView3.tag = 2;
            [alertView3 release]; 
        }
        else { UIAlertView *alert = [[UIAlertView alloc] initWithTitle:@"You're up to date!" message:@"There are no new regulations available at this time."  delegate:self cancelButtonTitle:@"OK" otherButtonTitles: nil];
            [alert show];
            [alert release];