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.

Sign up for GitHub

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

Jump to bottom

feat: bumped to flutter 3.3.0 #685

Merged
merged 6 commits into from
Sep 1, 2022
Merged

feat: bumped to flutter 3.3.0 #685

merged 6 commits into from
Sep 1, 2022

Conversation

juicycleff
Copy link
Owner

@juicycleff juicycleff commented Aug 31, 2022 •
edited
Loading

Description

Type of Change

  • ✨ New feature (non-breaking change which adds functionality)
  • 🛠️ Bug fix (non-breaking change which fixes an issue)
  • ❌ Breaking change (fix or feature that would cause existing functionality to change)
  • 🧹 Code refactor
  • ✅ Build configuration change
  • 📝 Documentation
  • 🗑️ Chore

@juicycleff juicycleff requested a review from Ahmadre August 31, 2022 19:21
@juicycleff juicycleff linked an issue Sep 1, 2022 that may be closed by this pull request
[Android] Prepare to revert Flutter 3.0 PlatformView workaround #667
Closed
@juicycleff juicycleff merged commit c884be0 into master Sep 1, 2022
@timbotimbo
Copy link
Collaborator

^2022.1.0+5 supports Flutter 3.0.0 and can only work with PlatformViewSurface for now. The implications of this is you have to pass useAndroidViewSurface: true to UnityWidget. You can track this flutter/flutter#103630. Currently working on supporting AndroidView.

@juicycleff
You might want to remove or update this section of the readme too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@Ahmadre Ahmadre Awaiting requested review from Ahmadre

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

[Android] Prepare to revert Flutter 3.0 PlatformView workaround
2 participants
@juicycleff @timbotimbo