I have found and corrected the issue affecting iOS 4.2 users in Dapp. Specifically, any changes to an on/off (boolean) setting were not being applied. The error was caused by a change in iOS 4.2 that now causes the iPhone to wait until the on/off animation is complete before applying the new isOn setting.
The patch has been submitted to Apple and should be available in the next week or so.
Thank you to everyone for your patience in this matter.To your app success!,
I’ve finally managed to get my hands on an iPhone 4. Blame our lack of supply in Australia . I was also happy to wait as I felt that the iPhone simulator would allow me to handle testing and debugging for iPhone 4 devices.
Of course, Murphy’s law stepped in and created a bug that only affected physical iPhone 4 devices with the latest iOS. From what I have gathered so far, the issue is that any ‘switch’ (boolean) settings are not being saved when a change is made. Now that I have an iPhone 4, I’ve been able to reproduce the issue and can submit a patch to Apple as soon as possible.
I’ll add a new post when the patch is submitted to Apple. Thank you to everyone for your patience.To your app success!,
I’ve received a few bug reports about a bug that has resurfaced where the positioning and size of UI Objects is not being handled correctly. In the past, this was due to ‘International’ settings where a comma is used instead of a decimal point to show decimal places. This was corrected by making sure to return ‘localized’ versions of strings/values. Unfortunately it is happening to some people again on iPhone 4 devices with latest OS, and this time I am unable to reproduce the issue on my end.
If possible, if you are able to successfully reproduce bugs through a series of steps then please report the issue to us at email@example.com
The questions that will help us find the issue are:
1. What iPhone model are you using?
2. Which version OS do you currently have installed?
3. If you have a non-english international setting, which international setting are you using?
4. What are the steps to reproduce the issue? (to allow troubleshooting and fixing)
On my side, I’ll be refactoring and improving the code which might correct some of the more isolated/rare bugs that pop up.To your app success!,
Just found an issue when trying to run Dapp on iPhone devices running OS 3.1.3 and earlier. Thank you to the user that reported the bug.
To our fellow developers out there, conditional statements on running OS 4.0 specific code is probably a good idea .
This patch is now in review with Apple.To your app success!,
Unfortunately, it seems that the latest iPad 3.2 OS is not compatible with iOS 4.0 which is what Dapp 1.2 had to be built with to support the iPhone 4 retina display.
Just waiting for the Apple Event today, hopefully they announce iPad OS 4.0. If not, then I’ll have to roll back Dapp to 3.1.3 OS which means Live Preview gets to stay but the retina display support will no longer work. As such, when Dapp 1.2.1 is available, this will be an optional upgrade for those using iPhone 4 devices.To your app success!,
Users with non-english international settings on their iPhone may experience issues with Dapp. This can be corrected by changing international settings to english. A patch to support international languages has been submitted to Apple and should be available soon.
Update: The patch is now available (Version 1.1.1) and should solve issues for our non-english users.To your app success!,
We have found a small issue with the code generation when exporting code from a project that has only one page or exporting code from page options. To fix this, find the following segment in the [PageName]ViewController.m file. The following example assumes a name of Page1 has been set.
// Link this view controller to our Dapp generated view
UIView *page1View = [[Page1View alloc] init];
self.view = page1View;
Replace the middle line that has the alloc/init code with the following code.
UIView *page1View = [[Page1View alloc] initWithParentViewController:self];
Please note that this only affects projects/designs with a single page or when using page options code export. This issue will be fixed in the Version 1.1.1 patch.To your app success!,
We have had two separate bug reports about a rare instance of users not being able to permanently create new objects in their pages. Unfortunately, we are unable to reproduce this bug. Even when testing with the same iPhone version and OS.
This is most likely due to some issue when inserting these objects into the database.
The next version of Dapp will include more robust error reporting features that will inform us of any database errors. Hopefully, through this we can track down the cause of this issue.
Please contact us at firstname.lastname@example.org if you are getting any errors so that we can address them as quickly as possible.
Update: This was an issue with non-english international settings. This has been addressed in an update currently in review with Apple.To your app success!,