Rider upgrade conflict with last-btime Follow
When upgrading from 2018.3.4 (183.6092.12) to 2019.1.1 (191.6733.985) an upgrade loop occurs due to the last-btime file being detected as modified. The only available solution listed is to ignore which then causes the installer to begin again and display the same dialog. The timestamp in my file is today "1557614990" so the updater must have modified it at some point.
Please sign in to leave a comment.