Sending Microphone input to SharePoint via Flow works on PC but not IOS?

[BrianHFASPS]

I followed instructions at Saving microphone audio recorded in PowerApps to SharePoint online - EnjoySharePoint and Save Audio Recording to SharePoint Online - YouTube to create a PowerApp + Flow to send Microphone to SharePoint library. It seems to be working fine on PC but the flow breaks when app is run on IOS. Not sure if this is a problem with what PowerApps is sending or how Flow is processing it?

In the Create File step of the flow I am getting this error:

InvalidTemplate. Unable to process template language expressions in action 'Create_file' inputs at line '1' and column '7894': 'The template language function 'base64ToBinary' was invoked with a parameter that is not valid. The value cannot be decoded from base64 representation.'.

[Anonymous]

Hi,

Think this is the same as what I was eluding to here: https://powerusers.microsoft.com/t5/Building-Power-Apps/Uploading-Audio-File-to-SharePoint-from-Powe...

Basically I am sure this will be because of the format IOS is storing the audio file. And the type is basically not  a valid URI to be converted to Binary.

So short of having an equivalent expression for the IOS type of audio file, converting it to a suitable audio format before adding, the error will persist.

If you could upload me an audio file, even if empty in the format that IOS provides it or let me know the format I would love to try it out. I know I could probably google/Bing the format but I don't do Apple lol.

[BrianHFASPS]

Thanks for the help and pointer to other issue which seems to be exact same. I don't know how I can get the audio out as it is recorded inside the PowerApp app player? Would I need a control in PowerApp app to save file to local storage? I just haven't done that before.

The method the other poster and I are using (I am guessing he followed same tutorial online) is in the OnStop of Microphone

Set(varJson,JSON(BehaviorRecord.Audio,IncludeBinaryData));
Set(strB64Audio, Mid(varJson,25,Len(varJson)-25));

Then in the submit

MicrophoneAudiotoSharePoint.Run(strB64Audio, Name)

I notice in your other post you are sending the IncludeBinaryData and then doing more processing in the flow maybe? Can you explain that and maybe that is where the issue is. The tweaking of the data / headers isn't consistent.

[Anonymous]

Yeah so for me, be it an audio or image upload we know SharePoint wants it as Binary.

So for me the IncludeBinaryData should be good as it is, but it isnt.

So the crucial step that always helps me is to use the Parse JSON action in Flow. Amongst getting my situations to work, it is extremely beneficial to determine what is coming through the front door to assist with troubleshooting. Or perhaps run it the once and use the Output as a sample payload to feed into the same Flow action, so that the properties can be easily selected throughout the rest of the Flow.

So first things first, I would ensure that your first Flow action after the trigger is Parse JSON and the value that is passed will be the output of the Microphone control wrapped in the JSON() function with the ,includebinarydata option.

If you could show me the output of that after the Flow has run that would be great to see. As it should include amongst other things the content type

[BrianHFASPS]

I added a display of the JSON data inside the app so I could see what was being seen before being passed to Flow. This is what I see:

On PC

On IOS

Definitely different encodings. How to deal with it though?

[BrianHFASPS]

I built the Parse JSON into Flow as you suggested and this is what it coming in.

In the tutorial that several have created they use this Set(strB64Audio, Mid(varJson,25,Len(varJson)-25));

Is it something as easy and simple as a different length of header due to length of webm vs. aac?

[BrianHFASPS]

I made it so the header is trimmed properly but it didn't help unfortunately. For some reason the aac base64 isn't being processed properly?

[BrianHFASPS · Accepted solution]

Ok so when I said I trimmed it properly I was wrong. Now I have trimmed it properly it does work. So to recap in case anyone else comes here to find this again.

1. The original code Set(strB64Audio, Mid(varJson,25,Len(varJson)-25)) was hard coded for the length of header specifically for webm audio, it was not a generic verion.
2. I tried Last(Split(varJson,",")).Result which was close and was generic. It neglected to clean up the trailing " though.
3. I settled on Left(Last(Split(varJson,",")).Result,Len(Last(Split(varJson,",")).Result)-1) which is really yucky but cleans of the trailing ".

The file that gets uploaded to SharePoint has .webm extension but internally is aac I think however SharePoint's media player seems to handle it fine. May not be the perfect solution but seems to work.

The next issue is somehow in doing all this I broke my playback audio control only on IOS. That is an issue for another day though.