tracker issue : CF-3713281

select a category, or use search below
(searches all categories and all time range)
Title:

"Uncaught cfclient is not initialized properly" error when running a shell app debug session

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/Duplicate

Reporter/Name(from Bugbase): Matt Gifford / Matt Gifford (Matt Gifford)

Created: 02/25/2014

Components: Mobile Support

Versions: 11.0

Failure Type: Non Functioning

Found In Build/Fixed In Build: PublicBeta /

Priority/Frequency: Critical / All users will encounter

Locale/System: ALL / Mac 10.9

Vote Count: 0

Duplicate ID:	CF-3713173

Problem Description:

After starting a new mobile / cfclient debug session and connecting the Shell App, I receive an error alert window with "Uncaught cfclient is not initialized properly".

Steps to Reproduce:

Start a new mobile cfclient debug session and connect to the shell app.

Actual Result:

This halts the debug session as no cfclient variables are processed.

Expected Result:

Any Workarounds:

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3713281

External Customer Info:
External Company:  
External Customer Name: Matt Gifford
External Customer Email:  
External Test Config: My Hardware and Environment details:

Attachments:

  1. February 26, 2014 00:00:00: 1_uncaught_cfclient_error.tiff

Comments:

This doesnt seem to be a consistent bug but it stops me from continuing with the debug session and therefore unable to continue work.
Comment by External U.
13213 | February 25, 2014 10:59:12 AM GMT
this people from the <cfclient> code generation team should research. The debugger works fine and hence it is throwing an appropriate exception. On discussion with Paul this is perhaps because someone is trying to load in the desktop browsers, plugins which only run in mobile., (Comment added from ex-user id:aahmad)
Comment by Adobe D.
13214 | March 04, 2014 03:27:02 AM GMT
I'm not sure what you mean by loading in desktop browser plugins, but in the code example that was running before this error was thrown I'm only loading in the connection.getType() and geolocation.getCurrent methods which are not restricted to the browser.
Comment by External U.
13215 | March 04, 2014 03:34:43 AM GMT