Just a swipe of the finger to add pictures and videos to your blog posts.

YouTube changed their API and it has caused the YouTube integration in Blogsy to stop working.

We are working on an update to work with the changes in the YouTube API. Once we have that update we will submit it to Apple and they take about a week to approve.


Are you getting the following error message when you drag in a photo from the “My Photo Stream” album?

In the latest iOS update Apple changed the way photos are handled again. Now, if the photo is not on the device and is just in Photostream then Blogsy is unable to pull the photo from the cloud and fetch the data to embed it. This is why this “PROBLEM” message is appearing.

The only way to resolve this is to replace the photo API with the new PhotoKit framework. But this is not a simple change. This will take a lot of work and the sales of Blogsy are not enough to cover the investment to do that. So this will be part of a new version of Blogsy and not just part of another free update.

The following is a workaround until that new version comes out.

1) When you drag in the photo and get the “PROBLEM” message you need to tap on the “Dismiss” button.

2) This will cause the Image Settings menu to open.

3) Tap somewhere outside the Image Settings menu and not on the image. This will close the Image Settings menu and the image will disappear because it cannot be fetched. But you will see a white box where the image should be.

4) Now double-tap somewhere inside this box where the image should be. This will cause the Image Settings menu to open for that missing photo. Scroll to the bottom of the Image Settings menu and tap on the “Delete” button. This will remove the embed code for that missing image from the HTML.

5) Close Blogsy and go to the Photos app on your iPad. Go to your “My Photo Stream” album and tap on the image you want to use in your blog post.

6) Tap on the little box with an arrow coming out of it in the bottom left corner of the screen. Choose all the photos that are in your photostream that you want to use in your blog post. Then tap on the option to “Save Image”. This will cause the photo(s) which is/are in your PhotoStream to be saved to your device in the “Camera Roll” album.

7) Now go back to Blogsy and drag in the photo from the “Camera Roll” album instead of from the “My Photo Stream” album.



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”.

Screen Shot 2014-12-26 at 9.41.44 PM

“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.

Happy Blogging,

The Blogsy Guys

The following is what can be found in this update.
And I would like to send a special thanks out to those that helped us test this. We could not reproduce the instant crashing problem here so there was no way for us to make changes to the code and see if it solved the problem. Fortunately there were some users willing to help us test this. After updating to our test version they reported that they were no longer having the instant crash problem. So we hope that this update is the solution but we can’t be 100% sure. If you have any crashing problem after updating to this version please email us right away to report it. info@fomola.com

[Bug Fixes]

1) Instant Crash: For some users Blogsy would instantly crash as soon as they tried to launch Blogsy. This crashing didn’t happen to everyone and didn’t happen all the time. Thanks for the volunteer testers we think this is fixed.


2) iCloud Photostream: iOS8 changed the way photos are handled on the iPad in iOS8 then changed it again in iOS 8.0.1 then changed it again in iOS 8.1. The change made it impossible for Blogsy to fetch the data required to embed a photo into a post from the PhotoStream. We programmed around this so now you can add photos from the Photostream album again.


3) “O” Online Posts UI Bug : The Online Posts menu would be broken if the iOS8 predictive keyboard was turned on. This is fixed.


4) Stuck on HTML Side : If you were running the latest version of Blogsy (Blogsy 4.1.10) on iOS7 then you would get stuck on the HTML Side if you flipped to the HTML Side. This is fixed.


This update was to address a change Flickr made in their API which would cause Blogsy to crash when you tapped on the Flickr icon in the dock. And you could not set up new Flickr accounts. Now Blogsy works with the new Flickr API so this will no longer happen.



If you have previously set up a Flickr account in Blogsy and you tap on the Flickr icon in the dock then you will get kicked out of Blogsy.

Or if you try to set up a new Flickr account in Blogsy you will see the following error message.

“Oops, Flickr doesn’t recognize the “frob” this application is trying to use.”

The reason for these problems is that Flickr has changed their API. This means we have to change the programming in Blogsy to work with the changed API then submit Blogsy to Apple for their approval.

I will update this post with our progress along the way.
We have fixed this and submitted the update to Apple. Apple usually takes no more than a week to approve updates. This update (Blogsy 4.3.5) will be in the App Store as soon as Apple approves it. 
Apple has approved the update so Blogsy 4.3.5 can now be found in the App Store.

If you have a Blogger blog and have Blogsy set to upload to your blog’s media library (a Picasa account) don’t update Blogsy to version 4.3.3.

We just discovered a problem with uploading to Picasa. As soon as we have more detailed information I will add it to this post.

5/23/2014 4:00pm

We figured out the bug and fixed it and submitted the update to Apple (Blogsy 4.3.4). 

One workaround until this update comes out would be to use some other app (there are many free apps that upload to Picasa) to upload photos to your Picasa account. Then from within Blogsy you can drag in those photos from the Picasa dock item to add them to your post and publish your post.

We’re very sorry for these troubles.
Apple has approved the update and now Blogsy 4.3.4 can be found in the App Store.

Recently Tumblr changed their OAuth callback from “http://xxx” to “https:/xxx”. This means that if you tried to set up a Tumblr blog then Tumblr would send back an error. This update fixes that so you will be able to set up a Tumblr blog again.

Also, in a unique set of steps Blogsy was not stripping out some junk HTML that iOS adds when typing in the webview. We fixed that so now that junk HTML gets stripped out in that situation.

We added one other bug fix to this update. If you try to add a link by going into the iOS popup bubble (instead of the drag-in method) and manually entering the URL in the Link Settings menu this could cause Blogsy to crash if you follow a certain set of steps. We have fixed this in this update.

Apple takes about a week to approve updates so this update will be in the App Store in about a week.



Tumblr has changed their OAuth callback URL from “http://xxx” to “https://xxx”. This means Tumblr sends back an error when trying to set up a blog. You can see what happens in the following screenshots when trying to set up a Tumblr blog.



This only effects people trying to set up their blog. If you have already set up your Tumblr blog in Blogsy then you will not have a problem.

We have fixed this so now Blogsy will work with either OAuth callback url (http, https).

We are adding one other fix to this update and then we will submit it to Apple. Apple takes about a week to approve updates and once they do then the update with these fixes will be in the App Store. I will do another blog post as soon as we submit this update to Apple and will update that blog post when Apple approves it.

 This issue has been fixed in Blogsy 4.3.3


Update 3/4/2014

Apple has expedited the approval so you can now find Blogsy 4.3.1 in the App Store. Please update right away.

Also, Apple is doing something strange with a double install in certain situations. So after updating please look at the bottom of the Settings menu in Blogsy to confirm you are running 4.3.1. If it shows 4.3 then go to the App Store and look for the update to 4.3.1.
Sorry for these problems!

Updated 3/1/2014 (10:02 local time)

Thank you very much everyone for your answers and help. Thanks to the crash reports we have figured out what the problem is. 
If you had turned off the Blogsy footer in the previous version then updated this caused the crash. So the people that had not turned off the footer are the ones that are not having this instant crash.
We have submitted the update to Apple and we requested them to expedite the approval so we can get the fix out sooner. If you wait for this update to come out then you will once again be able to get to your local drafts. If you decide to do a clean reinstall then you can use it now but know there are a few bugs which we have also fixed in this update.
Here is what is in this update.
1) The instant crash problem is fixed. This had to do with the footer being turned off by users in the previous version they were running.
2) WordPress setup crash. If a user tries to set up a self-hosted WordPress blog this can intermittently cause a crash. If you keep trying you will eventually be able to set up your blog. This update fixes this so it will not longer crash.
3) Turning off the footer will no longer cause a crash.
4) Tumblr and Post Info. menu crash. If the blog is set to Tumblr then you try to open the Post Info. menu it will cause a crash. Also if you try to switch to a Tumblr blog in the Post Info. menu this will cause a crash. This is fixed in this update. 

We are getting quite a few emails from users saying that after they update to the latest version of Blogsy (Blogsy 4.3) it crashes as soon as they tap on Blogsy to open it.

We need your input because we are not able to reproduce this problem. If we can’t reproduce it then there is nothing for us to fix.

Users have said that if they delete Blogsy off of their iPad then download it from the App Store again they no longer have the problem. But we don’t consider this a solution.

Obviously we did full testing before we submitted the update and didn’t have any crashing problem. But now people are reporting the following three crashes.

1) Trying to turn off the Blogsy footer causes a crash. We have already fixed this and it will be part of the next update.

2) Trying to add a self-hosted WordPress blog infrequently causes a crash. We have fixed this and it will be part of the next update. But this crash should be intermittent. So if you keep trying to set up your blog you should eventually be able to.

3) The instant crash mentioned above.

a) We installed Blogsy 4.2.9 on our iPad and created some local drafts.
b) We went to the App Store and updated Blogsy to 4.3. (The strange thing is that Apple updated it once to 4.2.9 then we had to update again to 4.3. Did anyone experience this? Multiple people have reported having this same experience. We are wondering if this is related to the problem. We don’t have any control over this so we will reach out to Apple about it.)
c) We launched Blogsy and did not experience the instant crashing problem. So we are not able to reproduce this problem.

There is no way to determine if everyone is experiencing this instant crash or if only some users are experiencing it. The fact that we cannot reproduce it would lead us to believe that not all users are experiencing this problem. So we need to figure out what is different.

Can you please email us as much detail as possible so we can get this fixed and submit the next version to Apple and ask them to hurry and approve it? If enough people provide information we may be able to find something that is common and it will help us track down the cause.

Our email address is info@fomola.com

a) What generation of iPad are you using?
b) What version of iOS are you running?
c) Is your iPad jailbroken?
d) Did you have any local drafts in Blogsy?
e) Did you have a post open that you were working on before updating?
f) Did you experience the double update that we experienced?
g) Any other details you can think of?

We are very sorry your are experiencing this problem. We are trying hard to figure it out.

Latest Information: 3/1/2014

We have now had about 30 people provide answers to the questions we asked above. Every question had variation in the answers so they don’t provide any information to reproduce the problem. We have also had emails from users saying they update and didn’t experience the instant crashing problem.

So here is the latest question and request.

1) Is your iPad a cellular version or not?

2) Can you send us the crash log? This may help us track down the cause.

1. Sync with iTunes

Crash logs are transferred to iTunes whenever you sync your device. Plug in your device, and launch iTunes to complete the sync.

2. Retrieve the Crash Log

Mac Users:

  1. Open Finder (found in the Dock)
  2. Click on the ‘Go’ menu at the top of your screen, and select ‘Go to Folder’
  3. Type (or paste): ~/Library/Logs/CrashReporter/MobileDevice/
  4. Open the folder with the same ‘name’ as your device. (Note: your device name appears in iTunes on the left side, under ‘Devices’).
  5. You will see at least one item starting with ‘Blogsy’. Copy the latest one to your desktop.
  6. Send us an email (info@fomola.com) with that file attached.

Windows Vista/7 Users

  1. Open any Windows Explorer Window (My Computer, My Documents, etc.)
  2. Enter %appdata%, and press enter
  3. Navigate to Roaming > Apple computer > Logs > CrashReporter > Mobile Device > *Device Name*. (Note: your device name appears in iTunes on the left side, under ‘Devices’)
  4. You will see at least one item starting with ‘Blogsy’. Copy the latest one to your desktop.
  5. Send us an email (info@fomola.com) with that file attached.

Windows XP Users

  1. Locate your Application Data folder. To see instructions on how to find this folder, click here: eHow: How to access the Application Data Folder
  2. Navigate to Apple computer > Logs > CrashReporter > Mobile Device > *Device Name*. (Note: your device name appears in iTunes on the left side, under ‘Devices’)
  3. You will see at least one item starting with ‘Blogsy’. Copy the latest one to your desktop.
  4. Send us an email (info@fomola.com) with that file attached.