It appears you coded your app using Companion 2.56u and expect it to be automatically accepted by GooglePlay. That will not happen. You probably are using the option to send messages or make phone calls automatically. Google does not permit that normally. You must petition them and explain why you are programming those capabilities. My understanding is they reject most such petitions.
You can post your app on other market places possibly or distribute you app using other methods but cannot use GooglePlay without issues.
You can avoid updating permissions by compiling your app using Companion 2.56, but then your app cannot automatically send sms or phone calls directly.
Peter provided this explanation:
We implemented conditional permissions for Texting and PhoneCall components so apps built with MIT App Inventor will be compliant with new Google Play Store policies. By default, apps using the Texting and PhoneCall components will now launch the device’s default texting and dialer apps. Most app inventors will be able to continue using the existing blocks for their apps.
If you want to build apps that respond to SMS or phone calls, or directly initiate a text or call, you may do so. To send a message or start a call, use the SendMessageDirect and MakePhoneCallDirect blocks, respectively. Receiving texts and calls continues to behave as it did. However, apps built with these behaviors will trigger additional review when being submitted to Google Play.
NOTE: The MIT AI2 Companion distributed through the Google Play Store cannot use the SendMessageDirect or MakePhoneCallDirect blocks. Attempting to use them will result in a permission error. This is due to restrictions imposed by Google (see paragraph above about changes in Google Policies). If you download the Companion directly from the MIT App Inventor system (via the “Help->Companion Information” Menu option) you will get a version that does work with the “Direct” blocks.