One of features that I like a lot on GameAnalytics is the Error Tracking.
I was wondering if I can get the scene name in the log event.
Example, I have the following error on my panel:
?:0: attempt to index field 'contentBounds' (a nil value) stack traceback: ?: in function '?' ?: in function 'gotoScene' ?: in function \<?:420\> ?: in function \<?:7\> ?: in function \<?:218\>
So, based only on the log, I don’t have idea where the error is in the code.
Are you using composer or storyboard?
Storyboard, and I also set the useStoryboard flag.
Looking at https://github.com/coronalabs/framework-storyboard-legacy/ it appears this is due to the currentScene missing it’s contentBounds table. currentScene could be nil or some how written over.
I don’t know much about the gameAnalytics plugin and how they are using storyboard. But it’s referring to the current scene when it tries to make an image out of the current scene to transition. Do you have content in the scene? (stuff in the group?)
Rob
Hummm. I didn’t know that it was related to storyboard since I have some other that does not mention anything storyboard-related like:
?:0: attempt to index field '?' (a nil value) stack traceback: ?: in function '?' ?: in function '\_listener' ?: in function \<?:141\> ?: in function \<?:218\>
But, answering your question, I don’t what scene the problem is (that is what want to know 
), but yes, I would have content since all my scenes have content.
Since GameAnalytics says that stores all scene names, I was wondering if they could give us the scene name prior to the error happening.
The scene name is passed along in the area field, which means you can filter all error events by area in the Quality tab. Use the dropdown in the upper-left. Would that work for you?
Hi Ana.
Yes, that works. Thanks.
Just a feedback, would be nice to have a column with that info in the Error Table. In my case for example, the filter has 11 scenes and I need to go one by one to identify the errors on each scene.
Best
It may not be a storyboard related issue. I was going on the fact you said scenes and I was looking for when contentBounds might be nil to generate that error.
Glad you got your answer.
Rob
Ah, that will be next quest. You were already ahead :). I was first just trying to find on what scene the error was happening. Now the fun part begins…
Are you using composer or storyboard?
Storyboard, and I also set the useStoryboard flag.
Looking at https://github.com/coronalabs/framework-storyboard-legacy/ it appears this is due to the currentScene missing it’s contentBounds table. currentScene could be nil or some how written over.
I don’t know much about the gameAnalytics plugin and how they are using storyboard. But it’s referring to the current scene when it tries to make an image out of the current scene to transition. Do you have content in the scene? (stuff in the group?)
Rob
Hummm. I didn’t know that it was related to storyboard since I have some other that does not mention anything storyboard-related like:
?:0: attempt to index field '?' (a nil value) stack traceback: ?: in function '?' ?: in function '\_listener' ?: in function \<?:141\> ?: in function \<?:218\>
But, answering your question, I don’t what scene the problem is (that is what want to know ), but yes, I would have content since all my scenes have content.
Since GameAnalytics says that stores all scene names, I was wondering if they could give us the scene name prior to the error happening.
The scene name is passed along in the area field, which means you can filter all error events by area in the Quality tab. Use the dropdown in the upper-left. Would that work for you?
Hi Ana.
Yes, that works. Thanks.
Just a feedback, would be nice to have a column with that info in the Error Table. In my case for example, the filter has 11 scenes and I need to go one by one to identify the errors on each scene.
Best
It may not be a storyboard related issue. I was going on the fact you said scenes and I was looking for when contentBounds might be nil to generate that error.
Glad you got your answer.
Rob
Ah, that will be next quest. You were already ahead :). I was first just trying to find on what scene the error was happening. Now the fun part begins…