Adam St. John

My 'has many through' associations work well except that the "updated_by" user is only stored on the parent model when using accepts_nested_attributes_by.

This is also relevant when accessing the linkedIN v1 api. `https://api.linkedin.com/v1/people/~:(id,emailAddress,firstName,lastName,numConnections,pictureUrl)` LinkedIN won't register properly if the url is encoded. @axelson - any chance you can elaborate on your solution?...

This does occur for me in production from background sidekiq workers. Subsequent retries are successful.

It's the same error as what @prockport has mentioned. It would seem that the `@ssl` object is nil during the `stop_persistence` method. backtrace: ``` /bundler/gems/pushmeup-9a95b551296d/lib/pushmeup/apns/core.rb:31 in "stop_persistence" /app/jobs/sitata_jobs/push_notifications_job.rb:36 in "push_ios"...

@prockport, that makes sense and so I will most likely restructure our sidekiq worker. That said, I think the root of this problem might be the fact that `@sock`, `@ssl`,...

@NicosKaralis, I took a stab at redesigning the gem based on feedback and pull requests from others. Please take a look here: https://github.com/Sitata/pushmeup/tree/ios8 It uses a new structure with a...

@maxintech, Not completely sure what you mean by Amazon refactory, but I did refactor all of the current providers.

@maxintech - sounds great. Let me know how it goes.

@maxintech - how do you place the PEM in memory?

@maxintech, interesting. Well, if you want to take a kick at it, I could see a simple solution as making a `set_pem` method on the gateway that sets `@pem_file` directly...