Skip to content

What triggeres updating the ./libs folder (Buggy Behavior) #690

@NathanaelA

Description

@NathanaelA

I ran into the same issue as Leo #689 and unfortunately I had updated actually updated my Telerik UI and they had fixed the issue in the TUI; but the ./Libs folder had apparently STILL cached the old version with the old Info.plist file.

How do you force the ./Libs folder to refresh from the node_modules versions? After several tries (tns build --release/--for-device, tns prepare, deleting libs, etc) I still couldn't make TNS update it. I finally just manually copied over all the new versions of everything manually from node_modules into the ./libs folders, and was good. But this behavior REALLY concerns me. You create the ./libs folder but don't seem to be maintaining it when the node_modules are updated... (I had three frameworks in there outdated, two from TUI and the main widgets).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions