Winter 15 Release - Causing failure

[Nick-Propertybase]

Can you think of anything in the latest Salesforce 15 release that would cause a conflict or stop Angular from fully initializing or bringing in any of the visualforce pages defined in the routes ?

I am 99% certain that the update is causing the issue. I have confirmed this in 2 two different orgs by refreshing the sandbox and it works as expected, overnight it updates and it no longer works.

Background:
I have started several different projects in different Salesforce sandbox orgs, and on a new refresh and only adding/updating the basics(custom settings, routes, visualforce pages for routes, and dummy content) everything works perfectly as expected.

Problem:
However as soon as the Sandbox is auto-updated to the Winter 15 release the seed App does not work. It doesn't seem to initialize, I have confirmed that all resources are available for both cases local and server side via chrome developer tools. There are zero javascript errors, and it seems to recognize the seedApp visualforce page, and it brings in the angular_config page with a session id and the resource URL. It seems like the Routes are never initialized to bring in any of the other visualforce pages defined. Also, using the ng-Inspector(chrome app), it only shows the app name(seedApp) and $rootScope with nothing underneath it.

If you have any idea of what could cause this please let me know, this has me stumped. I have learned a lot from this project, and I plan to write up a tutorial for others as well as contribute. I would be happy to grant access to the Sandbox to give you a full view of the project. I just refreshed one of my other orgs Sandboxes that stopped working, and I do the bare minimum setup again to have a working example for comparison sake and post the code on Github and/or grant access.

Please let me know if there is any other information that I can provide.

Thanks,
Nick

[Kevin Poorman]

Nick,

I unfortunately to not have access to a winter15 release sandbox. If you can hook me up with credentials to an org where I can see this happening, and test / poke around that’d be fantastic!

-Kevin

-- 
Kevin Poorman
Sent with Airmail

On January 23, 2015 at 5:04:17 AM, Nick-Propertybase ([e-mail]) wrote:

Can you think of anything in the latest Salesforce 15 release that would cause a conflict or stop Angular from fully initializing or bringing in any of the visualforce pages defined in the routes ?

I am 99% certain that the update is causing the issue. I have confirmed this in 2 two different orgs by refreshing the sandbox and it works as expected, overnight it updates and it no longer works.

Background:
I have started several different projects in different Salesforce sandbox orgs, and on a new refresh and only adding/updating the basics(custom settings, routes, visualforce pages for routes, and dummy content) everything works perfectly as expected.

Problem:
However as soon as the Sandbox is auto-updated to the Winter 15 release the seed App does not work. It doesn't seem to initialize, I have confirmed that all resources are available for both cases local and server side via chrome developer tools. There are zero javascript errors, and it seems to recognize the seedApp visualforce page, and it brings in the angular_config page with a session id and the resource URL. It seems like the Routes are never initialized to bring in any of the other visualforce pages defined. Also, using the ng-Inspector(chrome app), it only shows the app name(seedApp) and $rootScope with nothing underneath it.

If you have any idea of what could cause this please let me know, this has me stumped. I have learned a lot from this project, and I plan to write up a tutorial for others as well as contribute. I would be happy to grant access to the Sandbox to give you a full view of the project. I just refreshed one of my other orgs Sandboxes that stopped working, and I do the bare minimum setup again to have a working example for comparison sake and post the code on Github and/or grant access.

Please let me know if there is any other information that I can provide.

Thanks,
Nick

—
Reply to this email directly or view it on GitHub.

[Nick-Propertybase]

--removed login info

Angular app has been renamed to 'spa' rather than seedApp - direct url to
the main page is below. Right now it is set to get resources from the
server side, but feel free to change it, or I can change it if it is easier
to troubleshoot with the local server.

https://c.cs10.visual.force.com/apex/spa

Please let me know if need any other info from me.

Thanks,
Nick

On Fri, Jan 23, 2015 at 7:46 AM, Kevin Poorman [e-mail]
wrote:

Nick,

I unfortunately to not have access to a winter15 release sandbox. If you
can hook me up with credentials to an org where I can see this happening,
and test / poke around that’d be fantastic!

-Kevin

Kevin Poorman
Sent with Airmail

On January 23, 2015 at 5:04:17 AM, Nick-Propertybase (
[e-mail]) wrote:

Can you think of anything in the latest Salesforce 15 release that would
cause a conflict or stop Angular from fully initializing or bringing in any
of the visualforce pages defined in the routes ?

I am 99% certain that the update is causing the issue. I have confirmed
this in 2 two different orgs by refreshing the sandbox and it works as
expected, overnight it updates and it no longer works.

Background:
I have started several different projects in different Salesforce sandbox
orgs, and on a new refresh and only adding/updating the basics(custom
settings, routes, visualforce pages for routes, and dummy content)
everything works perfectly as expected.

Problem:
However as soon as the Sandbox is auto-updated to the Winter 15 release
the seed App does not work. It doesn't seem to initialize, I have confirmed
that all resources are available for both cases local and server side via
chrome developer tools. There are zero javascript errors, and it seems to
recognize the seedApp visualforce page, and it brings in the angular_config
page with a session id and the resource URL. It seems like the Routes are
never initialized to bring in any of the other visualforce pages defined.
Also, using the ng-Inspector(chrome app), it only shows the app
name(seedApp) and $rootScope with nothing underneath it.

If you have any idea of what could cause this please let me know, this has
me stumped. I have learned a lot from this project, and I plan to write up
a tutorial for others as well as contribute. I would be happy to grant
access to the Sandbox to give you a full view of the project. I just
refreshed one of my other orgs Sandboxes that stopped working, and I do the
bare minimum setup again to have a working example for comparison sake and
post the code on Github and/or grant access.

Please let me know if there is any other information that I can provide.

Thanks,
Nick

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub
#2 (comment)
.

[Nick-Propertybase]

I updated Angular and all of the resources in the ng directory to the latest version 1.3.10 and everything seems to be working.

I am going to do another isolated test to confirm that was the problem. I will report back.

Thanks.