You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 23, 2023. It is now read-only.
Did you verify whether this issue has already been reported here?
_Yes
Tell us about the problem
Generally, livesync does not respond to changes made to code.
Which platform(s) does the issue occur on?
_iOS
_Windows
Provide the following version numbers that the issue occurs with:
NativeScript Sidekick: 1.19.2-v.2019.11.18.2
NativeScript CLI: 6.2.2
CLI extension nativescript-cloud: 1.19.3
CLI extension nativescript-starter-kits: 0.3.5
Tell us how to recreate the issue in as much detail as possible
Start the application ..
Get an app running on a connected device.
Make changes to the code. For example, add <Label class="badge-text" text="Message" textWrap="true" ></label>
or, change return ("Firebase data is: " + JSON.stringify(this.getlevelUps().data) );
to return ("Firebase data is: " );
Observe no change in device display or in error generated in console logs.
Does this issue happen every time?
No
Send the client logs
The text was updated successfully, but these errors were encountered:
Please, provide the details below:
Did you verify whether this issue has already been reported here?
_Yes
Tell us about the problem
Generally, livesync does not respond to changes made to code.
Which platform(s) does the issue occur on?
_iOS
_Windows
Provide the following version numbers that the issue occurs with:
Tell us how to recreate the issue in as much detail as possible
Start the application ..
Get an app running on a connected device.
Make changes to the code. For example, add
<Label class="badge-text" text="Message" textWrap="true" ></label>
or, change
return ("Firebase data is: " + JSON.stringify(this.getlevelUps().data) );
to
return ("Firebase data is: " );
Observe no change in device display or in error generated in console logs.
Does this issue happen every time?
No
Send the client logs
The text was updated successfully, but these errors were encountered: