getTimeline called twice on load

When I run my widget from xcode I see getTimeline is called twice for some reason.

It's called the first time, then after it returns a timeline it's called again. The logs have the following message:

"-[EXSwiftUI_Subsystem beginUsing:withBundle:] unexpectedly called multiple times."

It takes about 0.5 seconds for the first getTimeline call to return so it doesn't seem like the OS should try to call this method again so quickly (my timeline entries all have times in the future so they shouldn't request the widget to load immediately)

Is this a bug, or expected? Seems to happen every time I run the widget.
Up vote post of markdaws Down vote post of markdaws
3.1k views
Posted by
markdaws
Reply
Add a Comment

Replies

Might be the same to me ios 14 widget + REST api
Posted by
rtyuigvuiuybibiuboi
Up vote reply of rtyuigvuiuybibiuboi Down vote reply of rtyuigvuiuybibiuboi
Add a Comment
Same
Posted by
BobbyKing
Up vote reply of BobbyKing Down vote reply of BobbyKing
Add a Comment
Mark here.
Posted by
_hm
Up vote reply of _hm Down vote reply of _hm
Add a Comment
So it's been 4 month and still no answer or fix from Apple, what a shame.
In my device it's getting called 3 times, regardless if I returned a quick time line or not.
Posted by
mohen
Up vote reply of mohen Down vote reply of mohen
Add a Comment

Not sure if I answer your question but I found out that getTimeline gets called for each widget size.

  • If I have only small widget (one or two or more) getTimeline called once.
  • If I have small widget and medium widget, getTimeline called twice.
  • If I have small, medium, large widgets, getTimeline called three times.

Took me couple of days to know this. It might be helpful to you.

Posted by
Boonyawat
Up vote reply of Boonyawat Down vote reply of Boonyawat

  • I only have one size I have an api call in the Gettimeline I still see it being called 3 times...

    —
    hopye

  • One size, but how many of it? Do you have any widgets on Lock Screen?

    —
    Boonyawat
Add a Comment

Same here. Any news about it?

Posted by
wangjin1990
Up vote reply of wangjin1990 Down vote reply of wangjin1990
Add a Comment

Same here in 2023

Posted by
DmitryK1
Up vote reply of DmitryK1 Down vote reply of DmitryK1
Add a Comment

Hello, Any resolution for this issue, I am still facing in Nov. 2023?

Posted by
KSH-09
Up vote reply of KSH-09 Down vote reply of KSH-09
Add a Comment