Still banging my head against this one....

After much testing here's where I stand.

I did get the servicesframework loaded by implicitly making the call from the code behind view.cs file. Although I'm not thinking this had anything to do with it now.

If I log in as admin everything works as it should both when using a mobile client as well as using a desktop web client. However, if I log in as a normal user everything works fine only on the desktop web client. It's as if the servicesframework does not function at all on the mobile client if a normal user is logged in. It doesn't appear to be skin related as I have tried several different skins  on the mobile page with the same results.

For testing I put the following snippet at the top of my javascript block of code:

$(document).ready(function() {
	var servicesFramework = $.ServicesFramework(1244);
	var token = servicesFramework.getAntiForgeryValue();
	oken);
	});

After some head scratching I thought would add to this thread. I have been bumping into this issue while developing a module that will live on a page that does not use the search skin object. If the search skin object is on the page or a user is logged into the site the client side ServicesFramework is available. Otherwise the ServicesFramework is not available.

What I found is that as long as I insert this line of code in the Page_Load event of the module's .ascx file the ServicesFramework JS will be available regardless of the skin or skin objects used. I believe any module using the client side services framework js should implement it as you cannot be sure that a skin will be using any particular skin object. I hijacked it from the Search Skin Object code here: https://github.com/dnnsoftware/Dnn.Pl...

DotNetNuke.Framework.ServicesFramework.Instance.RequestAjaxAntiForgerySupport();

If you have this error on an existing page, and you are not developing your own module, I would suggest trying to add the search skin object onto the skins page even if you are not using it. It will force the loading of the client side Services Framework js albeit with some bloat.

Instead of $.ServicesFramework() try change it to jQuery.ServiceFramework()
This solve my issue.