The problem seems to be when a new user first installs the app they don't have the latest version of the PDF document behaviours, as the refresh and open in native app buttons also aren't showing, but have been set to those particular pages. If I go into my app and re-save one of PDF pages then they all work the next time the user tries to access them. Anyone else seen this behaviour, and is there any way to make sure new users see the latest version of the PDF pages? Maybe a forced refresh?

Hi, That particular screen is indeed capable of a Forced Refresh flag, and you can set it from the Advanced Properties section of that screen in your control panel. That would be my suggestion. If you are calling the PDF from a URL, then it will obviously not exist in the app the first time a user opens the app. After it gets called the first time, it is cached on the device, and won't get called again until that screen is refreshed. If the PDF is going to be static (won't change at all), I'd recommend making it a local file and shipping it with the app. Thanks! Mark

Hi Mark, thanks for getting back to me so quickly. The plan was indeed to ship the PDF with the app, but somehow the project got archived without the relevant files in bt_docs (and accepted by Apple, which was surprising), and so once I realised that was the case I switched to emergency remote PDFs instead, but this is causing problems as you can see. I'm going to do a v1.1 update with the docs in-app tonight. The Forced Refresh didn't work, a fresh installation of the app shows the 'old' PDF page which only has an email button, not the current configuration of three buttons. So, the fact that the URL isn't present in the problem, but can you think of why simply re-saving one of the PDF pages corrects the problem app-wide?

Hi David, Off hand I can't think of why it's working the way you suggest. I'd probably need to load it in Xcode and watch the console. But, at least you know what the solution is! Mark

Just a thought, if the app was originally designed to load the PDF locally (which it was but I had to change it to a remote URL once I realised the PDFs hadn't been included in the archive) would that cause the issue? I can't get the screens to automatically refresh and correct the issue for new users at the moment, hopefully 1.1 with the PDFs baked in won't take too long to be approved.

I have my PDF in BT_Docs in Xcode. Same name in Buzztouch. But I get the not downloaded in iOS, so I renamed my pdf to sample.pdf. Now I get teh old sample pdf but not my pdf. So I must be doing one dumb thing... Appreciate your help Scott

Hey Scott, Couple of things here: * Make sure there are no spaces in the filename for your PDF * Ensure that you have the local PDF filename specified in your Configuration Panel, and that it's just the filename...no references to folders or anything * Do a Project...Clean after you have added the file to Xcode, and before you compile next time. Let me know if that helps! Mark

Thanks, Mark. book.pdf is all I have. Will do the Project clean

no luck... :( so strange. I embedded a video np...

Hi Scott, Indeed very strange! Can you post some output from your Debug Console at the time you try to open the PDF screen? That way we can see what Xcode thinks is going on, and continue our debugging from there. Here's a document that describes how to set that up : http://www.buzztouch.com/resources/Problem_Reporting_and_Basic_Debug_v1.0.pdf Thanks! Mark

Buzztouch 1.5 Xcode 4.2 iOS 5 Left it over night. Xcode slept great as did Buzztouch and today the book showed up as embedded :^) Thanks for all your help Scott

Very strange, but glad it was resolved! If it comes up again, throw some output from the Console here, and we can debug it. Have a good weekend! Mark