This question is locked. New answers and comments are not allowed.
Hi,
We're testing the CLI, but we're receiving an error when trying to login. No window is opened and the attached message is shown.
An important information is that our network uses a proxy, and I'm guessing this is the reason. We'll test it without the proxy as soon as we can, but, being this the case, I think this should be resolved.
Thanks in advance.
We're testing the CLI, but we're receiving an error when trying to login. No window is opened and the attached message is shown.
An important information is that our network uses a proxy, and I'm guessing this is the reason. We'll test it without the proxy as soon as we can, but, being this the case, I think this should be resolved.
Thanks in advance.
6 Answers, 1 is accepted
0
Hi Fernando,
Thanks for your feedback.
Currently the login command sends requests to app.icenium.com in order to log you in. This should open a page in your default browser which requests credentials.
If you are using proxy maybe will be a good idea to whitelist this domain. You can investigate further what is causing this issue by using Fiddler. You can track your request and check their status.
If you need any further assistance I will be glad to help.
Regards,
Zdravko
Thanks for your feedback.
Currently the login command sends requests to app.icenium.com in order to log you in. This should open a page in your default browser which requests credentials.
If you are using proxy maybe will be a good idea to whitelist this domain. You can investigate further what is causing this issue by using Fiddler. You can track your request and check their status.
If you need any further assistance I will be glad to help.
Regards,
Zdravko
0
Fernando
Top achievements
Rank 1
answered on 24 Jun 2014, 07:44 PM
Hi, Zdravko,
It was indeed a proxy related issue. It would be nice if the CLI took the proxy information from the machine, but I'm glad there is at least a workaround for that.
However, another problem is occurring. When the Simulator is started, it crashes immediately and leaves a file named debug.log on the root of the project, containing:
[0624/163201:WARNING:resource_bundle.cc(303)] locale_file_path.empty()
[0624/163202:ERROR:cef_context.cc(458)] No localized string available for id 18020
The second line is repeated for about a hundred times, with different 'ids'.
The strange is that the Simulator worked fine for a couple of times, but now it crashes every time. I reinstalled the CLI and recreated the project, but to no use.
Thanks again!
It was indeed a proxy related issue. It would be nice if the CLI took the proxy information from the machine, but I'm glad there is at least a workaround for that.
However, another problem is occurring. When the Simulator is started, it crashes immediately and leaves a file named debug.log on the root of the project, containing:
[0624/163201:WARNING:resource_bundle.cc(303)] locale_file_path.empty()
[0624/163202:ERROR:cef_context.cc(458)] No localized string available for id 18020
The second line is repeated for about a hundred times, with different 'ids'.
The strange is that the Simulator worked fine for a couple of times, but now it crashes every time. I reinstalled the CLI and recreated the project, but to no use.
Thanks again!
0
Fernando
Top achievements
Rank 1
answered on 24 Jun 2014, 08:00 PM
I've managed to track down the source of the problem. If I remove this line from the project (the one that is created by default):
The Simulator stops crashing. I think that's also related to our network, but it may be helpful to someone.
<script src="https://maps.googleapis.com/maps/api/js?v=3.exp&sensor=true"></script>The Simulator stops crashing. I think that's also related to our network, but it may be helpful to someone.
0
Hi Fernando,
Thank you for sharing your solution with our community. I also think this might be a consequence from the proxy you are using.
Regarding the warning / error you reported I want to say that we are aware of them and they should not be at fault.
Regards,
Zdravko
Telerik
Thank you for sharing your solution with our community. I also think this might be a consequence from the proxy you are using.
Regarding the warning / error you reported I want to say that we are aware of them and they should not be at fault.
Regards,
Zdravko
Telerik
Share what you think about AppBuilder and Telerik Platform with us in our feedback portal, so we can become even better!
0
Fernando
Top achievements
Rank 1
answered on 05 Aug 2014, 03:07 PM
Sorry for bumping this thread, but I found an issue that I think it's related.
We tried to access our internal API server through the IP adress (a simple AJAX request), and this makes the simulator crash. When using the server name, it works OK. The stranger is that, when the simulator is opened by the AppBuilder IDE, it doesn't crash if using the server IP.
We tried to access our internal API server through the IP adress (a simple AJAX request), and this makes the simulator crash. When using the server name, it works OK. The stranger is that, when the simulator is opened by the AppBuilder IDE, it doesn't crash if using the server IP.
0
Hello Fernando,
Would you provide us a sample that will help us to reproduce your Simulator issue?
This way we could investigate the cause and fix it.
Thanks in advance.
Regards,
Zdravko
Telerik
Would you provide us a sample that will help us to reproduce your Simulator issue?
This way we could investigate the cause and fix it.
Thanks in advance.
Regards,
Zdravko
Telerik
Visit the Telerik Verified Plugins Marketplace and get the custom Cordova plugin you need, already tweaked to work seamlessly with AppBuilder.