I've modified the code at http://www.switchonthecode.com/tutorials/using-core-plot-in-an-iphone-application to run on xcode4, I have a view that I put into my ConsoleViewControllor.xib with its class as CPTGraphHostingView.
Compiles great, at runtime however, I get a SIGABRT at line
hostingView.hostedGraph = graph; with the error
* Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[UIView setHostedGraph:]: unrecognized selector sent to instance 0x5910d40'
* Call stack at first throw:
Anyone else run into this issue? I'm more than willing to give you code and answer more questions. Thanks in advance!
Check the setup in your .xib again. -[UIView setHostedGraph:] means that Xcode created a UIView, not a CPTGraphHostingView.
Related
I have installed SmartStore on my server. everything is working fine except the add category module. when ever I try to Add or Edit any category an error pops saying :
Compilation Error Description: An error occurred during the
compilation of a resource required to service this request. Please
review the following specific error details and modify your source
code appropriately.
Compiler Error Message: CS0121: The call is ambiguous between the
following methods or properties:
'Telerik.Web.Mvc.UI.Fluent.GridToolBarCommandFactory.Template(System.Action>)'
and
'Telerik.Web.Mvc.UI.Fluent.GridToolBarCommandFactory.Template(System.Func,object>)'
Line 441: .ToolBar(commands => commands.Template(CategoryProductsGridCommands))
Please help me out. I m stuck :(
After working on it, we got the solution for this. So kindly try like this.
Hope will work
.ToolBar(commands => commands.Template(pp=>GridCommands(pp)))
let dataRef = database.collection("stores").document(store.id).collection("data").document("storeData")
var storeData: [String:Any] = [:]
storeData["seq"] = store.seq + 1
storeData["shiftSeq"] = store.shiftSeq + 1
dataRef.updateData(storeData)
I am receiving the following error when executing the above code. It was working fine until I upgraded to the latest version of Firebase/Firestore
* Assertion failure in -[FSTWriteStream startWithDelegate:], third_party/firebase/ios/Source/Firestore/Source/Remote/FSTStream.m:244
2017-12-08 10:48:47.819586-0500 centroOne[1833:473631] * Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'FIRESTORE INTERNAL ASSERTION FAILED: Delegate must be nil'
I removed a rule set that was attached to this document and the problem went away. The ruleset referenced a value in another document to make sure it existed.
I've faced this problem in swift recently and solved my problem by checking if documentId exists. In above case, please check store.id exits in your Firestore db and then run update method.
Environment: Symfony 2.8.1 with XAMPP Version 5.5.24 on Windows 7.
If I trigger a fatal error in a controller, anything as simple as $array = ; in production environment, I'm getting a default php error:
Parse error: syntax error, unexpected ';' in C:\xampp\htdocs\tgsupport-test\src\AppBundle\Controller\DefaultController.php on line 16
followed by symfony custom error page message. Obviously I'd want to avoid to show eorr info in production.
Moreover in prod.log I see a double critical error: under php.CRITICAL and request.CRITICAL. Is really useful to show the same error twice?
I'm using default configuration, indeed I just installed default framework without any custom setting and I triggered my error in AppBundle/DefaultController, so I was wondering if I'm missing anything.
I missed a php.ini configuration to avoid to display error messages in page.
I am loading one of the example apps from Shiny R into ShiniApps.io`
library(shinyapps)
shinyapps::setAccountInfo(name='xxx', token='xxx', secret='xxx')
deployApp("01_hello")
and then I get this error:
Error: Unhandled Exception: 'NoneType' object has no attribute 'getitem'
The app appeared in the web-page of Shinyapps.io as "undeployed".
Any clue what may be causing this error? the error is the same whether I run R 64 or 32 bit.
I had the same problem today. I wasn't able to successfully deploy a new app (getting the same error), but I was able to redeploy a previous app.
I have tried removing all packages and code from my new app (left only empty shinyServer and shinyUI functions uncommented) and still couldn't deploy.
Restarted R several times. Updated all packages. Nothing helped.
A few hours later I tried to deploy again and it passed without errors.
I know this is not exactly an answer but I suspect it was a server-side error because it failed during the "Starting instances" step of deployment.
So try to deploy it again, hope it works this time.
I was trying to redeploy a servlet I had recently undeployed but kept getting a org.apache.catalina.LifecycleException. Tomcat wasn't able to load the context properly.
This is what triggered the search:
FAIL - Unable to delete [/var/lib/tomcat7/conf/Catalina/localhost/app.xml].
The continued presence of this file may cause problems.
Here are the errors from the log catalina.out, rearranged to fit the column:
WARNING: Calling stop() on failed component [{0}] to trigger clean-up
did not complete.
org.apache.catalina.LifecycleException:
An invalid Lifecycle transition was attempted ([after_stop]) for
component [org.apache.catalina.startup.FailedContext#13150fc] in state
[FAILED]
WARNING: Error while removing context [/app]
java.lang.ClassCastException:
org.apache.catalina.startup.FailedContext cannot be cast to
org.apache.catalina.core.StandardContext
Scrolling back up, I noticed a whole list of SEVERE errors, beginning with:
SEVERE: Parse error in context.xml for /app
org.xml.sax.SAXParseException;
systemId: file:/etc/tomcat7/Catalina/localhost/app.xml/;
lineNumber: 1;
columnNumber: 1;
Content is not allowed in prolog.
This is not related to Cannot Undeploy a web-app completely in Tomcat 7 or Installing JSTL results in org.xml.sax.SAXParseException: Content is not allowed in prolog, though I wasted quite some time looking through these. Everything seemed to be as it should be, so I was stumped. Eventually, I solved it myself. My answer is below.
It turns out that I had deployed
/path/to/servlet/web/
as the XML Configuration file instead of
/path/to/servlet/website.xml
as Tomcat had been expecting.
A quick check in the saved form content of my other browser revealed this kickself error, so I am posting a Q and A here in the hope that this could save someone some time.
Please be careful when deploying manually, people.