This question is locked. New answers and comments are not allowed.
I apologize if this is a duplicate. I was away from the product for a week(ish) and now have the latest version of Graphite. Since the update I lose work fairly consistently. After approx every 5th save I start losing changes. I have only noticed it on css file, but for the most part that is what I had been changing. My changes are in my local version and the simulator will run fine, however, when I run through Ion the changes don't show up. Also, when I commit, the changes don't show in the changes dialog. To resolve, I close Graphite completely and restart. I am then prompted to Take Local or Take Cloud. If I Take Local, Ion still doesn't see the changes. If I Take Cloud, I lose my changes.
I just went over to Mist and the problem happened there as well.
The first 14 times I dealt with it, however, this is now a blocking issue. It happens too frequently and I don't know when it happens, because the simulator keeps working.
Update: I just noticed that the console is showing errors:
Server error: : https://app.icenium.com/api/filesystem/.../.../styles/main.css?validatorTypeName= : An error has occurred.
Please Help!
Thanks much,
Tom
btw - Overall I love the product.
I just went over to Mist and the problem happened there as well.
The first 14 times I dealt with it, however, this is now a blocking issue. It happens too frequently and I don't know when it happens, because the simulator keeps working.
Update: I just noticed that the console is showing errors:
Server error: : https://app.icenium.com/api/filesystem/.../.../styles/main.css?validatorTypeName= : An error has occurred.
Please Help!
Thanks much,
Tom
btw - Overall I love the product.
20 Answers, 1 is accepted
0
Hi Tom,
Thank you for the kind words about the product - much appreciated!
About the problem you've encountered - Graphite saves logs available in %LocalAppData%\Telerik\BlackDragon\Logs, so please zip and provide those logs for us to review (you can upload them to a free file server and give us a link). We also suggest running FiddlerCap (with the Decrypt HTTPS Traffic option enabled) before launching Graphite and save the HTTP requests Graphite performs to disk and send those our way as well. You can use FiddlerCap for capturing traffic when you test with Mist as well.
Greetings,
Steve
the Telerik team
Don't miss the Icenium May Release Keynote - sign up now!
Share feedback and vote for features on our Feedback Portal.
Thank you for the kind words about the product - much appreciated!
About the problem you've encountered - Graphite saves logs available in %LocalAppData%\Telerik\BlackDragon\Logs, so please zip and provide those logs for us to review (you can upload them to a free file server and give us a link). We also suggest running FiddlerCap (with the Decrypt HTTPS Traffic option enabled) before launching Graphite and save the HTTP requests Graphite performs to disk and send those our way as well. You can use FiddlerCap for capturing traffic when you test with Mist as well.
Greetings,
Steve
the Telerik team
Don't miss the Icenium May Release Keynote - sign up now!
Share feedback and vote for features on our Feedback Portal.
0
Tom
Top achievements
Rank 1
Rank 1
answered on 13 May 2013, 09:56 PM
Hey Steve,
Here is the log message after Graphite did not sync my change to the cloud. Thanks much!
Here is the log message after Graphite did not sync my change to the cloud. Thanks much!
[2013-05-13 16-47-38-49] Log (Info,None): Version 2013.2.508.1. Deployment location https://app.icenium.com.
[2013-05-13 16-47-39-15] Log (Info,None): Logged in as: tom@...
[2013-05-13 16-52-04-57] Log (Exception,High): System.AggregateException: A Task's exception(s) were not observed either by Waiting on the Task or accessing its Exception property. As a result, the unobserved exception was rethrown by the finalizer thread. ---> Telerik.BlackDragon.Client.ServerClient.HttpRequestExtendedException: Status code not successful: (500) Internal Server Error
Server stack trace:
at OperationExecutorExtensions.#S0c.#qb()
Exception rethrown at [0]:
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccess(Task task)
at OperationExecutorExtensions.#bEc.#qb()
--- End of inner exception stack trace ---
---> (Inner Exception #0) Telerik.BlackDragon.Client.ServerClient.HttpRequestExtendedException: Status code not successful: (500) Internal Server Error
Server stack trace:
at OperationExecutorExtensions.#S0c.#qb()
Exception rethrown at [0]:
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccess(Task task)
at OperationExecutorExtensions.#bEc.#qb()<---
0
Hi Tom,
Thanks for the additional information, however we would still need the log from Fiddler as well.
As you mention that the save problem occurs quite frequently, can you try running a ping to app.icenium.com with 2000 bytes of data i.e. run command prompt as Administrator and type "ping app.icenium.com -l 2000 -t" without the quotes and let it run for several minutes. Then check whether you have any packets lost and what is the %.
On a side note, I see that you've been trying Icenium for several months now and did not have such problems, has anything changed on your end prior the problem started to occur e.g. OS change, firewall etc.
As we're not able to reproduce this problem locally, we would appreciate any relevant information or steps to reproduce you could provide.
Regards,
Steve
the Telerik team
Don't miss the Icenium May Release Keynote - sign up now!
Share feedback and vote for features on our Feedback Portal.
Thanks for the additional information, however we would still need the log from Fiddler as well.
As you mention that the save problem occurs quite frequently, can you try running a ping to app.icenium.com with 2000 bytes of data i.e. run command prompt as Administrator and type "ping app.icenium.com -l 2000 -t" without the quotes and let it run for several minutes. Then check whether you have any packets lost and what is the %.
On a side note, I see that you've been trying Icenium for several months now and did not have such problems, has anything changed on your end prior the problem started to occur e.g. OS change, firewall etc.
As we're not able to reproduce this problem locally, we would appreciate any relevant information or steps to reproduce you could provide.
Regards,
Steve
the Telerik team
Don't miss the Icenium May Release Keynote - sign up now!
Share feedback and vote for features on our Feedback Portal.
0
Kevin
Top achievements
Rank 1
Rank 1
answered on 14 May 2013, 05:19 PM
Exact same issue here. Icenium is unusable to me at this point. Good thing i'm just fiddling around. If we were still invested in icenium for our app release there's no way it would go smoothly. Hope you guys get it worked out, i still plan to use icenium for personal project if the kinks get worked out.
Basically what I have to do now (using mist). is make my changes. CTRL A to select all. CTRL C to copy. ... hit save... see error.... reload browser. rinse repeat until the save works.
in response to responses on this thread/ No firewall changes. pinging server works fine. Nothing changed.
Basically what I have to do now (using mist). is make my changes. CTRL A to select all. CTRL C to copy. ... hit save... see error.... reload browser. rinse repeat until the save works.
in response to responses on this thread/ No firewall changes. pinging server works fine. Nothing changed.
0
Tom
Top achievements
Rank 1
Rank 1
answered on 15 May 2013, 01:12 PM
I ran the Ping for a couple mins and didn't look like there were any lost packets. I don't recall if something changed on my machine or not. The issue occurs both in my office and at my satellite office of Starbucks. I will be sending an email with the log attachment. I don't want to publish the link to the logs and post it here as anyone can see it and I'm not sure if it captured anything sensitive.
0
Hi guys,
Thank you both for the cooperation and logs that you've sent. We're working hard to track down this nasty culprit and once we do, we would issue a fix.
We appreciate your involvement and please excuse us for the inconvenience caused once again.
All the best,
Steve
the Telerik team
Don't miss the Icenium May Release Keynote - sign up now!
Share feedback and vote for features on our Feedback Portal.
Thank you both for the cooperation and logs that you've sent. We're working hard to track down this nasty culprit and once we do, we would issue a fix.
We appreciate your involvement and please excuse us for the inconvenience caused once again.
All the best,
Steve
the Telerik team
Don't miss the Icenium May Release Keynote - sign up now!
Share feedback and vote for features on our Feedback Portal.
0
Tom
Top achievements
Rank 1
Rank 1
answered on 15 May 2013, 08:57 PM
Sure Steve. Happy to help.
Just want to make sure you got my Mist logs. I emailed them to Anthony and Nick B. I know you are working on getting it resolved. Would you mind letting me know an ETA so that I can plan. If it is tomorrow, no big deal, but if it won't be till next week then I have to make adjustments in the mean time to be able to work.
Thanks so much,
Tom
Just want to make sure you got my Mist logs. I emailed them to Anthony and Nick B. I know you are working on getting it resolved. Would you mind letting me know an ETA so that I can plan. If it is tomorrow, no big deal, but if it won't be till next week then I have to make adjustments in the mean time to be able to work.
Thanks so much,
Tom
0
Hello Tom,
Steve
the Telerik team
Don't miss the Icenium May Release Keynote - sign up now!
Share feedback and vote for features on our Feedback Portal.
Thank you for sending the logs, the Internal Server error in them is a different known problem and could not be the cause for the saving mishaps. We’re still trying to reproduce the save problems locally, but without any luck so far and that is why we cannot commit on an ETA at this time.
One thing that is worth trying we forgot to mention is removing all cookies stored under the domain app.icenium.com from your browser and see if that makes any difference.
All the best,Steve
the Telerik team
Don't miss the Icenium May Release Keynote - sign up now!
Share feedback and vote for features on our Feedback Portal.
0
Tom
Top achievements
Rank 1
Rank 1
answered on 18 May 2013, 02:04 PM
Hey Steve,
I have been working for a bit today without issue and it was great. I had pulled down the latest build of Graphite and I though whew the issue is resolved. However, then happened again. Good news though I have more info for you. It seems that the issue happens when I'm using Ion. Here are the steps I can reproduce it:
1) Do work, Save.
2) Load app in Ion
3) Make change in Graphite and Save.
At this point I get Connection Interrupted error in the title bar. It says "Your last operation to the server was not successful. Please check your network and try again in a minute to prevent any data loss."
At this point I can still make changes and try to save but the connection interrupted error doesn't go away until I restart Graphite. I was able to go back to the dashboard, switch project, then switch back, make a change reload on Ion and see it. However, the connection error remains in the title bar. In order for me to know when I'm about to lose work, I have to close Graphite completely to get rid of the connection error.
Anyway, I hope that points you in a closer direction.
Take care,
Tom
I have been working for a bit today without issue and it was great. I had pulled down the latest build of Graphite and I though whew the issue is resolved. However, then happened again. Good news though I have more info for you. It seems that the issue happens when I'm using Ion. Here are the steps I can reproduce it:
1) Do work, Save.
2) Load app in Ion
3) Make change in Graphite and Save.
At this point I get Connection Interrupted error in the title bar. It says "Your last operation to the server was not successful. Please check your network and try again in a minute to prevent any data loss."
At this point I can still make changes and try to save but the connection interrupted error doesn't go away until I restart Graphite. I was able to go back to the dashboard, switch project, then switch back, make a change reload on Ion and see it. However, the connection error remains in the title bar. In order for me to know when I'm about to lose work, I have to close Graphite completely to get rid of the connection error.
Anyway, I hope that points you in a closer direction.
Take care,
Tom
0
Ryan
Top achievements
Rank 1
Rank 1
answered on 18 May 2013, 10:20 PM
Yeah I'm seeing the exact same problem described above. As long as I'm just working in Graphite with the simulator I'm fine. Soon as I open Mist or start trying to refresh the app on a device all hell breaks loose :( Just becomes chaos at that point trying to keep everything sync'd up. I have to copy and paste my work into text files before I shutdown Graphite because when it restarts and prompts me to Take Local or Take Cloud, even if I Take Local I can't ever commit those changes to version control
This is SERIOUS deal breaker guys...nobody's going to pay for a product that behaves in this manner. LiveSync is broken as of right now
This is SERIOUS deal breaker guys...nobody's going to pay for a product that behaves in this manner. LiveSync is broken as of right now
0
Kevin
Top achievements
Rank 1
Rank 1
answered on 19 May 2013, 05:46 PM
Yeah. this is still there for sure. I haven't even been using graphite, just mist and ion and i got all excited today my first save worked.... second save however... nope. Still as huge an issue as ever. I'm stuck in an endless cycle of copy, reload page, paste, save. rinse repeat anywhere from 10-20 times on average before a save goes through.
0
Hi guys,
We want to apologize for this unpleasant problem and want to assure you that we're working hard to identify and address it, which has proven to be a hard task since we cannot reproduce the problem. That is why we would appreciate if you email Graphite and Fiddler logs to our support at icenium com email after you start getting the problem consistently (i.e. if every couple of save attempts fail).
@Tom: "the connection interrupted" persistent error until Graphite is restarted is a known issue and is logged for fixing. You can ignore its presence at this time, but might check the exact error being reported in it, although the logs contain more accurate information and stack trace.
@Kevin: Thank you for the information you've provided so far. Please email us the requested logs, so we can review them locally.
@Ryan: As noted in Developing Your Project help article, developing a project simultaneously in both clients (Mist and Graphite) is not a supported scenario. If you encounter the problem of saving files when working in either client, please provide the respective logs, so we can investigate.
All the best,
Steve
the Telerik team
Don't miss the Icenium May Release Keynote - sign up now!
Share feedback and vote for features on our Feedback Portal.
We want to apologize for this unpleasant problem and want to assure you that we're working hard to identify and address it, which has proven to be a hard task since we cannot reproduce the problem. That is why we would appreciate if you email Graphite and Fiddler logs to our support at icenium com email after you start getting the problem consistently (i.e. if every couple of save attempts fail).
@Tom: "the connection interrupted" persistent error until Graphite is restarted is a known issue and is logged for fixing. You can ignore its presence at this time, but might check the exact error being reported in it, although the logs contain more accurate information and stack trace.
@Kevin: Thank you for the information you've provided so far. Please email us the requested logs, so we can review them locally.
@Ryan: As noted in Developing Your Project help article, developing a project simultaneously in both clients (Mist and Graphite) is not a supported scenario. If you encounter the problem of saving files when working in either client, please provide the respective logs, so we can investigate.
All the best,
Steve
the Telerik team
Don't miss the Icenium May Release Keynote - sign up now!
Share feedback and vote for features on our Feedback Portal.
0
Kevin
Top achievements
Rank 1
Rank 1
answered on 21 May 2013, 01:51 PM
I don't have fiddlercap or whatever and have not had time to sit down and set that up, sorry. No logs here as I only use Mist. I'll see if i can get around to figuring that out at some point. I find it hard to believe my scenario is any different than the others who have already provided logs, the same exact behavior occurs.
0
Ryan
Top achievements
Rank 1
Rank 1
answered on 21 May 2013, 02:04 PM
nice to see you guys are going to fix the Graphite disconnects..those are pretty annoying :( Happens to me at least a few times a day.
I wasn't developing in Mist and Graphite simultaneously. What I typically do, like when I'm working with some aspect of Cordova that doesn't work in the Simulator, is update my code in Graphite, save it, then refresh my app on my device to get the latest code. (holding down the menu on Android, the three finger press on iOS) That way I can at least "old school" debug what I'm doing on the actual device. That usually works really well, but here lately, it's very unstable for some reason?? I couldn't get it to work at all yesterday. So I basically have to go open up Mist, build for device, scan the barcode to get the latest version of my app on my phone for testing. Just wash, rinse, repeat over and over. I basically just gave up on doing oauth logins at the moment because of this issue since it just made testing a nightmare.
I wasn't developing in Mist and Graphite simultaneously. What I typically do, like when I'm working with some aspect of Cordova that doesn't work in the Simulator, is update my code in Graphite, save it, then refresh my app on my device to get the latest code. (holding down the menu on Android, the three finger press on iOS) That way I can at least "old school" debug what I'm doing on the actual device. That usually works really well, but here lately, it's very unstable for some reason?? I couldn't get it to work at all yesterday. So I basically have to go open up Mist, build for device, scan the barcode to get the latest version of my app on my phone for testing. Just wash, rinse, repeat over and over. I basically just gave up on doing oauth logins at the moment because of this issue since it just made testing a nightmare.
0
Hello Ryan,
Тhe sync you talk about is the Project LiveSync, in Graphite click on the Devices tab and see its status. If its off, delete the app from your device, and then re-deploy the app. Also right-click the first node in the Project Navigator and choose Build Settings and make sure that "Active Build Configuration" is either blank or "Debug". The "Release" build configuration strips out all Icenium-specific bits from your app's binary, so that might be a reason why LiveSync is not working for you.
If that does not help try the following:
Steve
the Telerik team
Don't miss the Icenium May Release Keynote - sign up now!
Share feedback and vote for features on our Feedback Portal.
Тhe sync you talk about is the Project LiveSync, in Graphite click on the Devices tab and see its status. If its off, delete the app from your device, and then re-deploy the app. Also right-click the first node in the Project Navigator and choose Build Settings and make sure that "Active Build Configuration" is either blank or "Debug". The "Release" build configuration strips out all Icenium-specific bits from your app's binary, so that might be a reason why LiveSync is not working for you.
If that does not help try the following:
- Export your project as .zip archive from the DashBoard -> the icon that looks like right turn sign.
- Create new project and add your exported project to it (Add -> From Archive).
- Connect your device.
Steve
the Telerik team
Don't miss the Icenium May Release Keynote - sign up now!
Share feedback and vote for features on our Feedback Portal.
0
Ryan
Top achievements
Rank 1
Rank 1
answered on 22 May 2013, 02:14 AM
I dunno what I did (cept dug around in some of those menus you mentioned) but it seems to be working again :)
0
Ryan
Top achievements
Rank 1
Rank 1
answered on 22 May 2013, 02:14 AM
I dunno what I did (cept dug around in some of those menus you mentioned) but it seems to be working again :)
0
Kevin
Top achievements
Rank 1
Rank 1
answered on 22 May 2013, 02:35 AM
Well mist is certainly still fubared. no change yet. i'll see about that fiddler thingy ma bobber in a bit
0
Hi all,
Share feedback and vote for features on our Feedback Portal.
We have just pushed a hot fix update to Icenium that has this bug fixed. Can you please try on your end and check if everything is working as expected?
Thanks all for your cooperation and take our apologies for your lost changes.
-sdobrev
Share feedback and vote for features on our Feedback Portal.
0
Tom
Top achievements
Rank 1
Rank 1
answered on 30 May 2013, 07:09 PM
Sweet!
I just tried it in Graphite and I don't get the error any more. Oh it is so nice.
However, when I started Graphite, I chose to skip the download so that I would be able to see it break first. Then I was going to try the new version and see it get fixed. When I tried it after clicking skip I did not get the error. Also, I now closed Graphite and tried to open it again but now I am not prompted to download the new version. Either it didn't actually skip and your fix worked, or it did skip and there was backend change (or my test is bad). Just wanted to give you some information on what's happening for me.
It seems to be working so I'm happy.
Thanks again!
Tom
I just tried it in Graphite and I don't get the error any more. Oh it is so nice.
However, when I started Graphite, I chose to skip the download so that I would be able to see it break first. Then I was going to try the new version and see it get fixed. When I tried it after clicking skip I did not get the error. Also, I now closed Graphite and tried to open it again but now I am not prompted to download the new version. Either it didn't actually skip and your fix worked, or it did skip and there was backend change (or my test is bad). Just wanted to give you some information on what's happening for me.
It seems to be working so I'm happy.
Thanks again!
Tom