1) We have had 8 people report that Blogsy is freezing when they try to publish a post.
2) From our analytics program we see that users are having a crashing problem about 3% of the time.
This is our current status in attempting to figure out these issues.
This is related to Blogsy trying to find photo added to the post from the PhotoStream. iOS provides an address to where this photo can be found but when Blogsy goes to find that photo in order to upload the photo it cannot be found at that address. This seems like a side effect of the fix in the previous update which allowed Blogsy to use PhotoStream photos in iOS8 with the old API. It order to bring back that ability we implemented it with a workaround. We are not sure yet if we can fix this without using the new PhotoKit API. We would only be able to use the new PhotoKit API that Apple added in iOS8 if we went through and reprogrammed many things.
This mean that the following workaround should be used if you are running into this freezing problem.
1) Go to the photos app on your iPad and move any photos that are in Photostream that you want to use in your blog post to your iPad photo library.
2) Go back to Blogsy and remove all the photos from your post.
3) Add the photos to your post again from the iPad photo library (not from the Photostream).
4) Publish your post.
We have spent several days trying to figure out the crashing.
First, the crashing problem, which is caused by storing & restoring local data is a very complicated problem. We’ve tried to fix it but thus far the changes haven’t worked. Blogsy uses a certain datastore which is called “NSUserDefault” to save & restore from local memory. But it seems that there is a bug in this iOS8 function. We found some other developers having the same problem. Here some links to their reports of this problem.
All the strike-through problems are related to this “NSUserDefault”.
“NSUserDefault” is integrated deeply into Blogsy’s programming so it can’t be quickly or easily changed without having many possible negative results in different areas. It is going to take some time to figure this out and make changes and test in order to assure the changes are solidly implemented.
1) Apple has shut down the store for developers through the 29th if December. So even if we were able to get this figured out we would not be able to submit it until after this date.
2) Apple takes about a week to approve updates. So once we submit the update it will take roughly a week to come out.
3) The sales of Blogsy are too low to pay our bills so everyone has had to go out and find other jobs. This means that this work has to be done in free time from our regular jobs. If Apple continues to make changes causing these issues and forcing us to continue to spend a lot of time updating then we may be forced to pull Blogsy from the App Store.
The Blogsy Guys