SwiftSoup: Archiving is stucked on Xcode 11 beta 3

In new Xcode 11 beta 3 carthage is stucked during building SwiftSoup. Same effect when archiving directly from Xcode

Some issue during optimizations. After disable optimizations for release everything works

SWIFT_OPTIMIZATION_LEVEL = -Onone

About this issue

Original URL
State: closed
Created 5 years ago
Reactions: 10
Comments: 29 (4 by maintainers)

Commits related to this issue

Fix scinfu#116 & scinfu#120 — committed to Jeehut/SwiftSoup by Jeehut 5 years ago
[simplify-cfg] When determining/searching for the end of a switch_enums diamond using single successors, make sure we do not have single block self-loop. Otherwise, we infinite loop. rdar://52131975 — committed to apple/swift by gottesmm 5 years ago

Most upvoted comments

And beta 5!

rectangular on Aug 1, 2019

Removed this framework and was able to publish on TestFlight. I migrated to another framework that works. Would you please teach me the name of framework you migrated?

tomxu2k on Sep 19, 2019

@catluc Please do not be too aggressive. This is an Swift Compiler bug and you should be angry with Apple not shipping the fix in Xcode GM.

funkenstrahlen on Sep 15, 2019

I know not everyone will be able to do this, but we just removed SwiftSoup and moved on with our lives.

I’m about to do the same. My app only uses SwiftSoup to retrieve a single URL from the src attribute of an <a href> tag within a bloated HTML document with huge commented-out sections and even those IE hacks from the 00’s in place. The guy who first developed my app seems to think dependencies are some sort of magic wand, free of consequences and hassles, use as many as you want, even for the most trivial reasons.

I asked my server-side team to provide a dedicated API that just gives me the URL straight; should be ready any time now.

SwiftSoup is a great framework for people who really need it. But personally, I believe using HTML (and web views) in a native app is an abomination, a necessary evil at best.

nicolas-miari on Sep 19, 2019

I know not everyone will be able to do this, but we just removed SwiftSoup and moved on with our lives.

kylebrowning on Sep 17, 2019

@funkenstrahlen I am still not seeing were is the agressive part, @scinfu was asking for feedback in previous comment, and i gave him that feedback, I am very aware that Apple needs to fix their bugs.

catluc on Sep 15, 2019

It’s still not in the master snapshot for 5.1

kylebrowning on Sep 4, 2019

It’s quite slow, but the latest swift toolchain snapshot has a fix for this issue: https://github.com/apple/swift/commit/378c6adbd625f1c1f568fa28116be3335506082f#diff-8b0154fba360507e6f59f3a0c8e98d1a

I can confirm that SwiftSoup archives when using this snapshot: https://github.com/apple/swift/releases/tag/swift-DEVELOPMENT-SNAPSHOT-2019-08-27-a

daniel-beard on Aug 28, 2019

Hey everyone, while it’s not a real fix, as noted by @Igor-Palaguta a workaround is to set the SWIFT_OPTIMIZATION_LEVEL to -Onone for release builds. I’ve done exactly that in my fork, feel free to use it’s master branch instead of this original repo when installing via Carthage or Accio. Unfortunately, it seems the will not merge it, as can be seen by my long term open PR https://github.com/scinfu/SwiftSoup/pull/117.

In Accio, use this entry instead:

.package(url: "https://github.com/Dschee/SwiftSoup.git", .branch("master")),

In Carthage, use that:

github "Dschee/SwiftSoup" "master"

Jeehut on Aug 26, 2019