Unanswered

Cannot Commit Using the new Preview Source Control

(0) Share

Report

Posted on by VG-15080911-0

I have a preview environment where I have an unmanaged solution. I have connected the unmanaged solution to the new Git Source Control feature still in preview. When I connect it has a bunch of changes to commit to my branch sitting in DevOps repos as expected. I click commit and after a while it gives me this error: The maximum request size of 26214400 bytes was exceeded. Parameter name: contentStream. Is there a way I can look at how big (File Size) my canvas app is so that I can see if this is the issue. I have also made sure my Policy on DevOps repos are to allow file size's up to the max which is 200mb. So if my canvas app is bigger than 200mb then yeah its understandable that it's not uploading but I can't find that info.

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (4)

Answers (0)

CU14012001-0 14 on at

Like (0)

Report

Cannot Commit Using the new Preview Source Control

Did you get this fixed? I've had a ticket in with Microsoft for 3 weeks and still waiting on a reply.

Was this reply helpful? Yes No
BlackSheep13 4 on at

Like (0)

Report

Cannot Commit Using the new Preview Source Control

We are having the same issues:

Was this reply helpful? Yes No
Suggested answer

BlackSheep13 4 on at

Like (0)

Report

Cannot Commit Using the new Preview Source Control

I think its on the FAQ's

FAQs about Dataverse and Git integration (preview)

Was this reply helpful? Yes No
VG-15080911-0 2 on at

Like (0)

Report

Cannot Commit Using the new Preview Source Control

@BlackSheep13 and @CU14012001-0

Have not found an answer to this yet.

Did try what the article said about trying to commit component by component and I tried but the Power App alone throws this issue.

Decided that legacy apps won't have this but that we will be building new ones in the preview environment as our dev environment for Source Control.

I haven't had the chance to look at if the issue still persists though so if it's been solved then just ignore this lol.

Have either of you come right yet potentially?

Was this reply helpful? Yes No