Relative date in widget gets cut off

Question

Created Aug ’20

Replies 6

Boosts 0

Views 1.6k

Participants 5

I'm trying to display a countdown in my widget, similar to the one shown in the WWDC video on WidgetKit. The problem is that as the time changes the font size is not readjusting and the text is getting cut off. Is there a workaround for this behavior?

Here is my code:

Code Block swiftVStack(alignment: .leading) {
		Text("\(entry.name) is in")
				.font(.subheadline)
     Text(entry.next.time, style: .relative)
         .font(.title2)
 	      .lineLimit(1)
 	      .frame(maxWidth: .infinity, alignment: .leading)
}
.minimumScaleFactor(0.5)
.allowsTightening(true)

Boost

Answer 1

CedricLnx OP

Aug ’20

I have a similar issue, my relative Text is concatenate with another and the width doesn't update so it's cut.

0

Answer 2

westerlund OP

Aug ’20

I'm in the same boat. I have forced the view to be as big as possible, but it's still cut off when going from 9 sec to 10 sec and 59 sec to 1 min, 0 sec and so on. It's a bummer, I really want to use this feature.

0

Answer 3

Brisket OP

Aug ’20

This is happening to me as well, with the concatenation occurring when there is plenty of space to render. I figure it's a bug but doesn't look like it's been fixed with beta 4. To test you can put the test alone in a contentview and it will still occur

1

Answer 4

crazyroo1 OP

Aug ’20

I ran into this issue as well. The workaround I'm using is to tack on a couple of \t (escape character for tabs) to my Text. This creates a flexible space for the relative date to fill up as it changes sizes.

Text("\(entry.date, style: .relative)\t\t\t\t")

0

Answer 5

ameir OP

Aug ’20

The release notes in beta 5 seem to indicate that this issue is fixed:

Resolved Issues in iOS & iPadOS 14 beta 5
Text(_ style:) no longer truncates. Text now has flexible width inside a widget. (60588299)

However, I'm still seeing the same behavior even after rebuilding my widget with Xcode 12 beta 5.

0

Answer 6

ameir OP

Aug ’20

still seeing this behavior in beta 6

0