R.swift: R.generated.swift is not re-generated without a clean build on 5.0.0 final

Hi!

I was using R.swift 5.0.0-alpha2 and had a unit test running validate() which was correctly failing whenever I had a wrong asset or font in a XIB:

XCTAssertNoThrow(try R.validate())

I’ve just updated to 5.0.0 and checked if that was still working before merging this update, but the test now passes for the same incorrect asset/font that fails the test at 5.0.0-alpha2.

Am I doing this in a deprecated way or is the feature broken?

Thanks!

About this issue

Original URL
State: closed
Created 5 years ago
Comments: 15 (6 by maintainers)

Most upvoted comments

R.swift 5.0.2 has been released, so I’m closing this issue.

From the updated migration documentation:

When using the New Build System: Configure the input/output files

When using the Legacy Build System: Add the flag --disable-input-output-files-validation Do not configure input/output files

If you’re still experience issues after upgrading to 5.0.2, please create a new issue.

tomlokhorst on Jan 22, 2019

Same issue here using the legacy build system

pgorzelany on Jan 14, 2019

Found the same problem. As a work-around, I added a second output file named R.dummy.swift which is never present and forces the script to always run. PS: I’m using the legacy build system because of other issues with development pods, I’m not sure if this changes behaviour with R.swift in any way.

rafaelnobrepd on Jan 8, 2019

Same problem here in 5.0.0 version.

fernandocruz on Jan 8, 2019