Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

iOS 15 Warnings in Xcode 13 when using ElegantCalendar #43

Closed
Danny-SS opened this issue Sep 24, 2021 · 4 comments
Closed

iOS 15 Warnings in Xcode 13 when using ElegantCalendar #43

Danny-SS opened this issue Sep 24, 2021 · 4 comments

Comments

@Danny-SS
Copy link

Issue
When running the Example project with Xcode 13, I am getting warnings in the console log:

ForEach<Array<String>, String, ModifiedContent<ModifiedContent<Text, _FrameLayout>, _EnvironmentKeyWritingModifier<Optional<Color>>>>: the ID T occurs multiple times within the collection, this will give undefined results!

There are six of these in a series logged the calendar is displayed.

iOS Version
This only happens when running against iOS 15. When I run against a simulator in iOS 14, it is quiet and I only get the expected messages from the Example project.

(This too is happening from my app that uses this package, but was easier and cleaner to verify this behavior in the include Example here).

I will try to hunt this down, but maybe someone else already has a solution. The calendar does appear to be working iOS 15 despite these warnings, but worry something in SwitUI may break the cause of this in the future.

@ThasianX
Copy link
Owner

Expected as new iOS version = new stuff unaccounted for in the original code. If you can hunt the solution down and add the changes to this pull request, that would be great

@Brahmah
Copy link

Brahmah commented Oct 9, 2021

This is because you have multiple events with the same Id. Does not appear to be a SwiftUI bug.

tompetit pushed a commit to tompetit/ElegantCalendar that referenced this issue Oct 4, 2022
@tompetit
Copy link

tompetit commented Oct 4, 2022

I was facing the same issue. Created a pull request, above

ThasianX pushed a commit that referenced this issue Oct 9, 2022
@ThasianX
Copy link
Owner

ThasianX commented Oct 9, 2022

#48 fixes this

@ThasianX ThasianX closed this as completed Oct 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants