-
Notifications
You must be signed in to change notification settings - Fork 76
Request format issue with iPad (iPhone working properly) #7
Comments
One step forward: actions not working are only those where a |
hummm |
Hello, sorry for the delay to getting back to you. I tryed a lot, but I could not reproduce this error. I've even refactored gems internals and specs, but could not find anything related. |
I released a new version with improvements in the user_agent list, ipad was included. Just be aware that after version 2.0 the method |
Hi tscolari ! I just rewrote that part of my app not to use respond_with ... and development went so much further I'm not able to reproduce it anymore. Anyway I'm upgrading and pinging back if any issues. I just realized I had this piece of code in an initializer. I was not the one who put this in place, nor why is it there. It might be related:
I'll comment that out and tell if something interesting is found. Regards! BTW, there's a typo in the README: Mobyllete per Mobylette. |
ups, I've fixed the typo! You got me with that initializer. There is one of those inside the gem too. |
Please give the version 3.0 a try, there was some internal changes in the resolvers. |
New version works great for me, thanks !!! |
That's great to hear! Sent via Hubroid |
Hi !
We're using mobylette to handle our mobile device requests under Rails 3.2.2, ruby 1.9.2 app. In our
ApplicationController
:It seems mobylette is failing to fallback views for iPads, while properly behaving with iPhones. Here is the error message for a failing iPad request:
I see a
formats => [:mobile]
that I guess should includehtml
as well ... just thinking out loud.Any ideas?
The text was updated successfully, but these errors were encountered: