I must concur. We have a massive number of Infopath/SharePoint applications. We need to rewite them in PowerApps since InfoPath is being depreciated in 2026. The main job of these apps is to collect files from the field. PowerApps can't seem to do this. There are Flows that will upload a file from the local drive, but require a hard coded password instead of taking the current user's credientials. How useless is that? How am I supposed to release an app to lots of users with these restrictions? I may have to actually write something that needs to be installed on over 250 people's PCs, just to upload a file.
Yes, the PowerApps team have released an attachment control, but limited to 10 meg, which is useless. They were worried about performance. Can kinda see why since Flow took over 30 minutes to post a 42 meg file and this was from a network PC, not a phone. What did they write Flows in, COBOL? Lucky for us, real time performance is not that big a deal, so we can live with it. However, not everyone would be in our situation.
I've been spending the last 2 days writing a web service wrapper around Flow to post a file to SharePoint from PowerApps. Everything works except getting PowerApps to load anything but an image to pass to the service. I may be able to somehow pass the file using the attachment control, but I don't know at this point. This situation is crazy.
Otherwise, I'm supportive of the effort as InfoPath has its own issues. However, InfoPath actually works and if we have to can write .Net code. Please, please, please remove the restriction on file upload and provide a way to create our own user defined function.