Skip to content

Merge Branch issue like 2 unknown error and grey screen came #5981

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

Closed
1 of 2 tasks
radhenvirtuous opened this issue Jun 12, 2025 · 2 comments
Closed
1 of 2 tasks

Merge Branch issue like 2 unknown error and grey screen came #5981

radhenvirtuous opened this issue Jun 12, 2025 · 2 comments

Comments

@radhenvirtuous
Copy link

Can we access your project?

  • I give permission for members of the FlutterFlow team to access and test my project for the sole purpose of investigating this issue.

Current Behavior

Merge Branch issue like 2 unknown error and grey screen came

Expected Behavior

it should display the error location or indications to solve but now it is grey out

Steps to Reproduce

while merging 2 branches

Reproducible from Blank

  • The steps to reproduce above start from a blank project.

Bug Report Code (Required)

IT40jsr1sK16sN9F7Yf+YfpsmSogN1A7aIAOmtt7aCosfZT2BLMcec/RVERtcMCqTW9cP1mjmWoW0cLlkt7DJfUBEAWbfKU41apyagKWVlOXeKasFJWgZmpBOJtYG2q94KW7gxJ/Lsh1V1IC7TqTf9mXTnTvJ5TIOUQsDa/LZO4=

Visual documentation

No doc

Environment

- FlutterFlow version: 6.0.15
- Platform: Web
- Browser name and version: Chrome Version 137.0.7151.70 (Official Build) (64-bit)
- Operating system and version affected: Windows OS

Additional Information

No response

@radhenvirtuous radhenvirtuous added the status: needs triage A potential issue that has not been confirmed as a bug. label Jun 12, 2025
Copy link
Collaborator

Hello!

This appears to be a project-specific issue. For this type of concern, we recommend reaching out to our support team directly via the in-app chat or by emailing [email protected]. They have the appropriate tools to assist you more effectively.

Please note that this GitHub issue tracker is intended for bugs that can be consistently reproduced in a new, blank project.

@Alezanello Alezanello self-assigned this Jun 12, 2025
@Alezanello Alezanello removed the status: needs triage A potential issue that has not been confirmed as a bug. label Jun 12, 2025
Copy link
Collaborator

Closing this issue since we haven't heard back from you. If you are still facing the problem please submit a new issue. Thank you!

@Alezanello Alezanello closed this as not planned Won't fix, can't repro, duplicate, stale Jun 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants