Vcard MMS file name is always “text 1”How do I fix an invalid content-type header in Twilio using node.js?Dumbfounded by Twilio API to send a simple text messageiOS failing to render vcf fileSend SMS Twilio API and WorpressWordPressTwilio - Send SMS Based on Body of Incoming MessageWhy is vcard not being received in replied sms when using MessagingResponse?How do I add an SMS from Twilio into Azure Table Storage using Logic AppTwilio SMS - what am I doing wrong?vCard file rendering as a txt file in iMessage with TwilioHow do I fix Twilio SMS send error when sending vcard via zapier

What's the origin of the concept of alternate dimensions/realities?

Break down the phrase "shitsurei shinakereba naranaindesu"

Resources to learn about firearms?

Magnetic thread storage?

Why doesn't Starship have four landing legs?

Padding a column of lists

My colleague treats me like he's my boss, yet we're on the same level

What are ways to record who took the pictures if a camera is used by multiple people?

Is Borg adaptation only temporary?

What is the motivation behind designing a control stick that does not move?

Storing milk for long periods of time

What checks exist against overuse of presidential pardons in the USA?

Should a TA point out a professor's mistake while attending their lecture?

Lob Logical Read and lob read-ahead reads in NCCI

Is it possible for a person to be tricked into becoming a lich?

Is it good practice to speed up and slow down where not written in a song?

Can UV radiation be safe for the skin?

Are sweatpants frowned upon on flights?

What is this "opened" cube called?

Necessity of tenure for lifetime academic research

Why is there no Disney logo in MCU movies?

I was given someone else's visa, stamped in my passport

Ask one verbal question to figure out who is blind and who is mute among three persons

Don't look at what I did there



Vcard MMS file name is always “text 1”


How do I fix an invalid content-type header in Twilio using node.js?Dumbfounded by Twilio API to send a simple text messageiOS failing to render vcf fileSend SMS Twilio API and WorpressWordPressTwilio - Send SMS Based on Body of Incoming MessageWhy is vcard not being received in replied sms when using MessagingResponse?How do I add an SMS from Twilio into Azure Table Storage using Logic AppTwilio SMS - what am I doing wrong?vCard file rendering as a txt file in iMessage with TwilioHow do I fix Twilio SMS send error when sending vcard via zapier






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








3















When sending a vcard file on an SMS message via Twilio using the mediaUrl option, it shows up on the iPhone with "text 1" next to the file as if "text 1" is the file name.



I have tried renaming the vcard file, using example vcard files, etc. No matter what the files show up as "text 1".



Example vcf



I have tried on iPhone 8 and 10. I have tried bare bones VCF files and full featured ones from Outlook and even example ones online such as http://www.w3.org/2002/12/cal/vcard-examples/john-doe.vcf - No matter what, they show up on iPhone as "text 1".



What can I do to make this be either the phone number or a name?



Edit --- After the comment from @philnash, I was able to add a content-disposition header to the file which now comes back in the headers as follows:



 Content-Disposition: attachment; name="John Doe"; filename="john-doe.vcf" 


Here is a screenshot from Fiddler:
Fiddler screenshot



I also renamed the file to a unique name and tried again in case Twilio or anywhere along the way was caching the old file. The header is there but the message still shows "text 1" on the iPhone.



In case it had something to do with Azure blob storage. I also coded an ASP.Net MVC file action that returns the file with the content dispostion headers - it also shows as "text 1" on iPhone.
IIS server










share|improve this question
































    3















    When sending a vcard file on an SMS message via Twilio using the mediaUrl option, it shows up on the iPhone with "text 1" next to the file as if "text 1" is the file name.



    I have tried renaming the vcard file, using example vcard files, etc. No matter what the files show up as "text 1".



    Example vcf



    I have tried on iPhone 8 and 10. I have tried bare bones VCF files and full featured ones from Outlook and even example ones online such as http://www.w3.org/2002/12/cal/vcard-examples/john-doe.vcf - No matter what, they show up on iPhone as "text 1".



    What can I do to make this be either the phone number or a name?



    Edit --- After the comment from @philnash, I was able to add a content-disposition header to the file which now comes back in the headers as follows:



     Content-Disposition: attachment; name="John Doe"; filename="john-doe.vcf" 


    Here is a screenshot from Fiddler:
    Fiddler screenshot



    I also renamed the file to a unique name and tried again in case Twilio or anywhere along the way was caching the old file. The header is there but the message still shows "text 1" on the iPhone.



    In case it had something to do with Azure blob storage. I also coded an ASP.Net MVC file action that returns the file with the content dispostion headers - it also shows as "text 1" on iPhone.
    IIS server










    share|improve this question




























      3












      3








      3








      When sending a vcard file on an SMS message via Twilio using the mediaUrl option, it shows up on the iPhone with "text 1" next to the file as if "text 1" is the file name.



      I have tried renaming the vcard file, using example vcard files, etc. No matter what the files show up as "text 1".



      Example vcf



      I have tried on iPhone 8 and 10. I have tried bare bones VCF files and full featured ones from Outlook and even example ones online such as http://www.w3.org/2002/12/cal/vcard-examples/john-doe.vcf - No matter what, they show up on iPhone as "text 1".



      What can I do to make this be either the phone number or a name?



      Edit --- After the comment from @philnash, I was able to add a content-disposition header to the file which now comes back in the headers as follows:



       Content-Disposition: attachment; name="John Doe"; filename="john-doe.vcf" 


      Here is a screenshot from Fiddler:
      Fiddler screenshot



      I also renamed the file to a unique name and tried again in case Twilio or anywhere along the way was caching the old file. The header is there but the message still shows "text 1" on the iPhone.



      In case it had something to do with Azure blob storage. I also coded an ASP.Net MVC file action that returns the file with the content dispostion headers - it also shows as "text 1" on iPhone.
      IIS server










      share|improve this question
















      When sending a vcard file on an SMS message via Twilio using the mediaUrl option, it shows up on the iPhone with "text 1" next to the file as if "text 1" is the file name.



      I have tried renaming the vcard file, using example vcard files, etc. No matter what the files show up as "text 1".



      Example vcf



      I have tried on iPhone 8 and 10. I have tried bare bones VCF files and full featured ones from Outlook and even example ones online such as http://www.w3.org/2002/12/cal/vcard-examples/john-doe.vcf - No matter what, they show up on iPhone as "text 1".



      What can I do to make this be either the phone number or a name?



      Edit --- After the comment from @philnash, I was able to add a content-disposition header to the file which now comes back in the headers as follows:



       Content-Disposition: attachment; name="John Doe"; filename="john-doe.vcf" 


      Here is a screenshot from Fiddler:
      Fiddler screenshot



      I also renamed the file to a unique name and tried again in case Twilio or anywhere along the way was caching the old file. The header is there but the message still shows "text 1" on the iPhone.



      In case it had something to do with Azure blob storage. I also coded an ASP.Net MVC file action that returns the file with the content dispostion headers - it also shows as "text 1" on iPhone.
      IIS server







      twilio






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Mar 28 at 15:48







      ericdc

















      asked Mar 27 at 23:05









      ericdcericdc

      9,6724 gold badges20 silver badges31 bronze badges




      9,6724 gold badges20 silver badges31 bronze badges

























          4 Answers
          4






          active

          oldest

          votes


















          1















          Twilio developer evangelist here.



          When Twilio provides the metadata for the MMS it does so based on the Content-Disposition header it gets when requesting the media from the URL you provide. When there isn't one available, it gets set to something generic, like "text 1" in this instance.



          To overcome this, you need to set the Content-Disposition response header on the file you are serving. Within this header, you can declare a name and a filename. I haven't been able to test this (I'm not in the US, so can't receive the MMS from Twilio) but I would guess that the name is used, though I would test with filename too.



          The header should look a bit like this:



          Content-Disposition: attachment; name="John Doe"; filename="john-doe.vcf"





          share|improve this answer

























          • Thanks for the help. I was able to add a content-disposition header to the file which now comes back in the headers as this but still does not work Content-Disposition: attachment; name="John Doe"; filename="john-doe.vcf" Here is a screenshot from Fiddler: screencast.com/t/ibYfN79HqN I also renamed the file to a unique name and tried again in case Twilio or anywhere along the way was caching the old file. The header is there but the message still shows "text 1". Do you have any other ideas?

            – ericdc
            Mar 28 at 14:52












          • I may be mistaken about using the name directive in the header. Try with only filename. Also, this is a vcard that we have tested and does work, with the name "Ashton", could you try this too? media.twiliocdn.com/AC648d937704b94309822578b85ff1227f/…

            – philnash
            Mar 30 at 5:49











          • I downloaded your example file, put it on my server - and it came through with the name "Ashton" - not the full name of Ashton Jones - just "Ashton". I then edited that file and changed one letter in the name to make it "Ashlon" and it came in as "text 1". I changed it back and it came as "Ashton". I then tried changing one number in the phone number from a 1 to a 2 and it again came in as "text 1". - So it worked with your exact file unchanged. I tried probably 50 variations of this. I updated my iPhone to 12.2 and now these come in right - even Ashton says Ashton Jones.

            – ericdc
            Mar 31 at 17:12











          • Well, I am fairly lost as to the cause there. Do your original tests work with iOS 12.2 too?

            – philnash
            Mar 31 at 23:47











          • As of right now, all tests work in 12.2.

            – ericdc
            Apr 1 at 18:30


















          1















          No fix, just adding that this experience also is replicated on Android 9 (Pie). The only discrepancy with the above is that the file is "text_1".






          share|improve this answer

























          • Upon further digging, I see that there may be a difference in the casing. Using the above listed "Ashton" example, the headers come back as content-disposition: attachment; filename="Ashton.vcf" and content-type: text/vcard, instead of something more like Content-type: text/vcard. I know HTTP headers are supposed to be case insensitive, but apache sometimes makes this an issue. Food for thought.

            – yoyoben
            Apr 16 at 21:21


















          1















          I tested this some as I was having the same issue. It appears once a Vcard has been sent, subsequent sends of the same Vcard result in text 1 being sent for the name of the Vcard. However, for sends to new recipients sends with the name. ...at least from my tests.






          share|improve this answer

























          • yeah...this was wrong. Upon further testing my users began only seeing "text 1".

            – MSF004
            Apr 7 at 16:40


















          0















          I spent a long time troubleshooting this. I was almost going to give up. But then I sent my own contact through mms from my phone to a number controlled by twilio so I could see what headers Twilio was capturing when originating directly from an iphone. That's when I noticed this important header:



          Content-Disposition: inline; filename="what-to-show.vcf"


          The key here is the "inline" argument, "attachment" doesn't work. Then my stuff came over on iOS just as I wanted. ("what-to-show" instead of "text 1"). Perfect!






          share|improve this answer



























            Your Answer






            StackExchange.ifUsing("editor", function ()
            StackExchange.using("externalEditor", function ()
            StackExchange.using("snippets", function ()
            StackExchange.snippets.init();
            );
            );
            , "code-snippets");

            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "1"
            ;
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function()
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled)
            StackExchange.using("snippets", function()
            createEditor();
            );

            else
            createEditor();

            );

            function createEditor()
            StackExchange.prepareEditor(
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader:
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            ,
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            );



            );













            draft saved

            draft discarded


















            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55387816%2fvcard-mms-file-name-is-always-text-1%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown

























            4 Answers
            4






            active

            oldest

            votes








            4 Answers
            4






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            1















            Twilio developer evangelist here.



            When Twilio provides the metadata for the MMS it does so based on the Content-Disposition header it gets when requesting the media from the URL you provide. When there isn't one available, it gets set to something generic, like "text 1" in this instance.



            To overcome this, you need to set the Content-Disposition response header on the file you are serving. Within this header, you can declare a name and a filename. I haven't been able to test this (I'm not in the US, so can't receive the MMS from Twilio) but I would guess that the name is used, though I would test with filename too.



            The header should look a bit like this:



            Content-Disposition: attachment; name="John Doe"; filename="john-doe.vcf"





            share|improve this answer

























            • Thanks for the help. I was able to add a content-disposition header to the file which now comes back in the headers as this but still does not work Content-Disposition: attachment; name="John Doe"; filename="john-doe.vcf" Here is a screenshot from Fiddler: screencast.com/t/ibYfN79HqN I also renamed the file to a unique name and tried again in case Twilio or anywhere along the way was caching the old file. The header is there but the message still shows "text 1". Do you have any other ideas?

              – ericdc
              Mar 28 at 14:52












            • I may be mistaken about using the name directive in the header. Try with only filename. Also, this is a vcard that we have tested and does work, with the name "Ashton", could you try this too? media.twiliocdn.com/AC648d937704b94309822578b85ff1227f/…

              – philnash
              Mar 30 at 5:49











            • I downloaded your example file, put it on my server - and it came through with the name "Ashton" - not the full name of Ashton Jones - just "Ashton". I then edited that file and changed one letter in the name to make it "Ashlon" and it came in as "text 1". I changed it back and it came as "Ashton". I then tried changing one number in the phone number from a 1 to a 2 and it again came in as "text 1". - So it worked with your exact file unchanged. I tried probably 50 variations of this. I updated my iPhone to 12.2 and now these come in right - even Ashton says Ashton Jones.

              – ericdc
              Mar 31 at 17:12











            • Well, I am fairly lost as to the cause there. Do your original tests work with iOS 12.2 too?

              – philnash
              Mar 31 at 23:47











            • As of right now, all tests work in 12.2.

              – ericdc
              Apr 1 at 18:30















            1















            Twilio developer evangelist here.



            When Twilio provides the metadata for the MMS it does so based on the Content-Disposition header it gets when requesting the media from the URL you provide. When there isn't one available, it gets set to something generic, like "text 1" in this instance.



            To overcome this, you need to set the Content-Disposition response header on the file you are serving. Within this header, you can declare a name and a filename. I haven't been able to test this (I'm not in the US, so can't receive the MMS from Twilio) but I would guess that the name is used, though I would test with filename too.



            The header should look a bit like this:



            Content-Disposition: attachment; name="John Doe"; filename="john-doe.vcf"





            share|improve this answer

























            • Thanks for the help. I was able to add a content-disposition header to the file which now comes back in the headers as this but still does not work Content-Disposition: attachment; name="John Doe"; filename="john-doe.vcf" Here is a screenshot from Fiddler: screencast.com/t/ibYfN79HqN I also renamed the file to a unique name and tried again in case Twilio or anywhere along the way was caching the old file. The header is there but the message still shows "text 1". Do you have any other ideas?

              – ericdc
              Mar 28 at 14:52












            • I may be mistaken about using the name directive in the header. Try with only filename. Also, this is a vcard that we have tested and does work, with the name "Ashton", could you try this too? media.twiliocdn.com/AC648d937704b94309822578b85ff1227f/…

              – philnash
              Mar 30 at 5:49











            • I downloaded your example file, put it on my server - and it came through with the name "Ashton" - not the full name of Ashton Jones - just "Ashton". I then edited that file and changed one letter in the name to make it "Ashlon" and it came in as "text 1". I changed it back and it came as "Ashton". I then tried changing one number in the phone number from a 1 to a 2 and it again came in as "text 1". - So it worked with your exact file unchanged. I tried probably 50 variations of this. I updated my iPhone to 12.2 and now these come in right - even Ashton says Ashton Jones.

              – ericdc
              Mar 31 at 17:12











            • Well, I am fairly lost as to the cause there. Do your original tests work with iOS 12.2 too?

              – philnash
              Mar 31 at 23:47











            • As of right now, all tests work in 12.2.

              – ericdc
              Apr 1 at 18:30













            1














            1










            1









            Twilio developer evangelist here.



            When Twilio provides the metadata for the MMS it does so based on the Content-Disposition header it gets when requesting the media from the URL you provide. When there isn't one available, it gets set to something generic, like "text 1" in this instance.



            To overcome this, you need to set the Content-Disposition response header on the file you are serving. Within this header, you can declare a name and a filename. I haven't been able to test this (I'm not in the US, so can't receive the MMS from Twilio) but I would guess that the name is used, though I would test with filename too.



            The header should look a bit like this:



            Content-Disposition: attachment; name="John Doe"; filename="john-doe.vcf"





            share|improve this answer













            Twilio developer evangelist here.



            When Twilio provides the metadata for the MMS it does so based on the Content-Disposition header it gets when requesting the media from the URL you provide. When there isn't one available, it gets set to something generic, like "text 1" in this instance.



            To overcome this, you need to set the Content-Disposition response header on the file you are serving. Within this header, you can declare a name and a filename. I haven't been able to test this (I'm not in the US, so can't receive the MMS from Twilio) but I would guess that the name is used, though I would test with filename too.



            The header should look a bit like this:



            Content-Disposition: attachment; name="John Doe"; filename="john-doe.vcf"






            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Mar 28 at 1:45









            philnashphilnash

            42.7k9 gold badges38 silver badges59 bronze badges




            42.7k9 gold badges38 silver badges59 bronze badges















            • Thanks for the help. I was able to add a content-disposition header to the file which now comes back in the headers as this but still does not work Content-Disposition: attachment; name="John Doe"; filename="john-doe.vcf" Here is a screenshot from Fiddler: screencast.com/t/ibYfN79HqN I also renamed the file to a unique name and tried again in case Twilio or anywhere along the way was caching the old file. The header is there but the message still shows "text 1". Do you have any other ideas?

              – ericdc
              Mar 28 at 14:52












            • I may be mistaken about using the name directive in the header. Try with only filename. Also, this is a vcard that we have tested and does work, with the name "Ashton", could you try this too? media.twiliocdn.com/AC648d937704b94309822578b85ff1227f/…

              – philnash
              Mar 30 at 5:49











            • I downloaded your example file, put it on my server - and it came through with the name "Ashton" - not the full name of Ashton Jones - just "Ashton". I then edited that file and changed one letter in the name to make it "Ashlon" and it came in as "text 1". I changed it back and it came as "Ashton". I then tried changing one number in the phone number from a 1 to a 2 and it again came in as "text 1". - So it worked with your exact file unchanged. I tried probably 50 variations of this. I updated my iPhone to 12.2 and now these come in right - even Ashton says Ashton Jones.

              – ericdc
              Mar 31 at 17:12











            • Well, I am fairly lost as to the cause there. Do your original tests work with iOS 12.2 too?

              – philnash
              Mar 31 at 23:47











            • As of right now, all tests work in 12.2.

              – ericdc
              Apr 1 at 18:30

















            • Thanks for the help. I was able to add a content-disposition header to the file which now comes back in the headers as this but still does not work Content-Disposition: attachment; name="John Doe"; filename="john-doe.vcf" Here is a screenshot from Fiddler: screencast.com/t/ibYfN79HqN I also renamed the file to a unique name and tried again in case Twilio or anywhere along the way was caching the old file. The header is there but the message still shows "text 1". Do you have any other ideas?

              – ericdc
              Mar 28 at 14:52












            • I may be mistaken about using the name directive in the header. Try with only filename. Also, this is a vcard that we have tested and does work, with the name "Ashton", could you try this too? media.twiliocdn.com/AC648d937704b94309822578b85ff1227f/…

              – philnash
              Mar 30 at 5:49











            • I downloaded your example file, put it on my server - and it came through with the name "Ashton" - not the full name of Ashton Jones - just "Ashton". I then edited that file and changed one letter in the name to make it "Ashlon" and it came in as "text 1". I changed it back and it came as "Ashton". I then tried changing one number in the phone number from a 1 to a 2 and it again came in as "text 1". - So it worked with your exact file unchanged. I tried probably 50 variations of this. I updated my iPhone to 12.2 and now these come in right - even Ashton says Ashton Jones.

              – ericdc
              Mar 31 at 17:12











            • Well, I am fairly lost as to the cause there. Do your original tests work with iOS 12.2 too?

              – philnash
              Mar 31 at 23:47











            • As of right now, all tests work in 12.2.

              – ericdc
              Apr 1 at 18:30
















            Thanks for the help. I was able to add a content-disposition header to the file which now comes back in the headers as this but still does not work Content-Disposition: attachment; name="John Doe"; filename="john-doe.vcf" Here is a screenshot from Fiddler: screencast.com/t/ibYfN79HqN I also renamed the file to a unique name and tried again in case Twilio or anywhere along the way was caching the old file. The header is there but the message still shows "text 1". Do you have any other ideas?

            – ericdc
            Mar 28 at 14:52






            Thanks for the help. I was able to add a content-disposition header to the file which now comes back in the headers as this but still does not work Content-Disposition: attachment; name="John Doe"; filename="john-doe.vcf" Here is a screenshot from Fiddler: screencast.com/t/ibYfN79HqN I also renamed the file to a unique name and tried again in case Twilio or anywhere along the way was caching the old file. The header is there but the message still shows "text 1". Do you have any other ideas?

            – ericdc
            Mar 28 at 14:52














            I may be mistaken about using the name directive in the header. Try with only filename. Also, this is a vcard that we have tested and does work, with the name "Ashton", could you try this too? media.twiliocdn.com/AC648d937704b94309822578b85ff1227f/…

            – philnash
            Mar 30 at 5:49





            I may be mistaken about using the name directive in the header. Try with only filename. Also, this is a vcard that we have tested and does work, with the name "Ashton", could you try this too? media.twiliocdn.com/AC648d937704b94309822578b85ff1227f/…

            – philnash
            Mar 30 at 5:49













            I downloaded your example file, put it on my server - and it came through with the name "Ashton" - not the full name of Ashton Jones - just "Ashton". I then edited that file and changed one letter in the name to make it "Ashlon" and it came in as "text 1". I changed it back and it came as "Ashton". I then tried changing one number in the phone number from a 1 to a 2 and it again came in as "text 1". - So it worked with your exact file unchanged. I tried probably 50 variations of this. I updated my iPhone to 12.2 and now these come in right - even Ashton says Ashton Jones.

            – ericdc
            Mar 31 at 17:12





            I downloaded your example file, put it on my server - and it came through with the name "Ashton" - not the full name of Ashton Jones - just "Ashton". I then edited that file and changed one letter in the name to make it "Ashlon" and it came in as "text 1". I changed it back and it came as "Ashton". I then tried changing one number in the phone number from a 1 to a 2 and it again came in as "text 1". - So it worked with your exact file unchanged. I tried probably 50 variations of this. I updated my iPhone to 12.2 and now these come in right - even Ashton says Ashton Jones.

            – ericdc
            Mar 31 at 17:12













            Well, I am fairly lost as to the cause there. Do your original tests work with iOS 12.2 too?

            – philnash
            Mar 31 at 23:47





            Well, I am fairly lost as to the cause there. Do your original tests work with iOS 12.2 too?

            – philnash
            Mar 31 at 23:47













            As of right now, all tests work in 12.2.

            – ericdc
            Apr 1 at 18:30





            As of right now, all tests work in 12.2.

            – ericdc
            Apr 1 at 18:30













            1















            No fix, just adding that this experience also is replicated on Android 9 (Pie). The only discrepancy with the above is that the file is "text_1".






            share|improve this answer

























            • Upon further digging, I see that there may be a difference in the casing. Using the above listed "Ashton" example, the headers come back as content-disposition: attachment; filename="Ashton.vcf" and content-type: text/vcard, instead of something more like Content-type: text/vcard. I know HTTP headers are supposed to be case insensitive, but apache sometimes makes this an issue. Food for thought.

              – yoyoben
              Apr 16 at 21:21















            1















            No fix, just adding that this experience also is replicated on Android 9 (Pie). The only discrepancy with the above is that the file is "text_1".






            share|improve this answer

























            • Upon further digging, I see that there may be a difference in the casing. Using the above listed "Ashton" example, the headers come back as content-disposition: attachment; filename="Ashton.vcf" and content-type: text/vcard, instead of something more like Content-type: text/vcard. I know HTTP headers are supposed to be case insensitive, but apache sometimes makes this an issue. Food for thought.

              – yoyoben
              Apr 16 at 21:21













            1














            1










            1









            No fix, just adding that this experience also is replicated on Android 9 (Pie). The only discrepancy with the above is that the file is "text_1".






            share|improve this answer













            No fix, just adding that this experience also is replicated on Android 9 (Pie). The only discrepancy with the above is that the file is "text_1".







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Apr 4 at 16:17









            yoyobenyoyoben

            213 bronze badges




            213 bronze badges















            • Upon further digging, I see that there may be a difference in the casing. Using the above listed "Ashton" example, the headers come back as content-disposition: attachment; filename="Ashton.vcf" and content-type: text/vcard, instead of something more like Content-type: text/vcard. I know HTTP headers are supposed to be case insensitive, but apache sometimes makes this an issue. Food for thought.

              – yoyoben
              Apr 16 at 21:21

















            • Upon further digging, I see that there may be a difference in the casing. Using the above listed "Ashton" example, the headers come back as content-disposition: attachment; filename="Ashton.vcf" and content-type: text/vcard, instead of something more like Content-type: text/vcard. I know HTTP headers are supposed to be case insensitive, but apache sometimes makes this an issue. Food for thought.

              – yoyoben
              Apr 16 at 21:21
















            Upon further digging, I see that there may be a difference in the casing. Using the above listed "Ashton" example, the headers come back as content-disposition: attachment; filename="Ashton.vcf" and content-type: text/vcard, instead of something more like Content-type: text/vcard. I know HTTP headers are supposed to be case insensitive, but apache sometimes makes this an issue. Food for thought.

            – yoyoben
            Apr 16 at 21:21





            Upon further digging, I see that there may be a difference in the casing. Using the above listed "Ashton" example, the headers come back as content-disposition: attachment; filename="Ashton.vcf" and content-type: text/vcard, instead of something more like Content-type: text/vcard. I know HTTP headers are supposed to be case insensitive, but apache sometimes makes this an issue. Food for thought.

            – yoyoben
            Apr 16 at 21:21











            1















            I tested this some as I was having the same issue. It appears once a Vcard has been sent, subsequent sends of the same Vcard result in text 1 being sent for the name of the Vcard. However, for sends to new recipients sends with the name. ...at least from my tests.






            share|improve this answer

























            • yeah...this was wrong. Upon further testing my users began only seeing "text 1".

              – MSF004
              Apr 7 at 16:40















            1















            I tested this some as I was having the same issue. It appears once a Vcard has been sent, subsequent sends of the same Vcard result in text 1 being sent for the name of the Vcard. However, for sends to new recipients sends with the name. ...at least from my tests.






            share|improve this answer

























            • yeah...this was wrong. Upon further testing my users began only seeing "text 1".

              – MSF004
              Apr 7 at 16:40













            1














            1










            1









            I tested this some as I was having the same issue. It appears once a Vcard has been sent, subsequent sends of the same Vcard result in text 1 being sent for the name of the Vcard. However, for sends to new recipients sends with the name. ...at least from my tests.






            share|improve this answer













            I tested this some as I was having the same issue. It appears once a Vcard has been sent, subsequent sends of the same Vcard result in text 1 being sent for the name of the Vcard. However, for sends to new recipients sends with the name. ...at least from my tests.







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Apr 4 at 22:25









            MSF004MSF004

            162 bronze badges




            162 bronze badges















            • yeah...this was wrong. Upon further testing my users began only seeing "text 1".

              – MSF004
              Apr 7 at 16:40

















            • yeah...this was wrong. Upon further testing my users began only seeing "text 1".

              – MSF004
              Apr 7 at 16:40
















            yeah...this was wrong. Upon further testing my users began only seeing "text 1".

            – MSF004
            Apr 7 at 16:40





            yeah...this was wrong. Upon further testing my users began only seeing "text 1".

            – MSF004
            Apr 7 at 16:40











            0















            I spent a long time troubleshooting this. I was almost going to give up. But then I sent my own contact through mms from my phone to a number controlled by twilio so I could see what headers Twilio was capturing when originating directly from an iphone. That's when I noticed this important header:



            Content-Disposition: inline; filename="what-to-show.vcf"


            The key here is the "inline" argument, "attachment" doesn't work. Then my stuff came over on iOS just as I wanted. ("what-to-show" instead of "text 1"). Perfect!






            share|improve this answer





























              0















              I spent a long time troubleshooting this. I was almost going to give up. But then I sent my own contact through mms from my phone to a number controlled by twilio so I could see what headers Twilio was capturing when originating directly from an iphone. That's when I noticed this important header:



              Content-Disposition: inline; filename="what-to-show.vcf"


              The key here is the "inline" argument, "attachment" doesn't work. Then my stuff came over on iOS just as I wanted. ("what-to-show" instead of "text 1"). Perfect!






              share|improve this answer



























                0














                0










                0









                I spent a long time troubleshooting this. I was almost going to give up. But then I sent my own contact through mms from my phone to a number controlled by twilio so I could see what headers Twilio was capturing when originating directly from an iphone. That's when I noticed this important header:



                Content-Disposition: inline; filename="what-to-show.vcf"


                The key here is the "inline" argument, "attachment" doesn't work. Then my stuff came over on iOS just as I wanted. ("what-to-show" instead of "text 1"). Perfect!






                share|improve this answer













                I spent a long time troubleshooting this. I was almost going to give up. But then I sent my own contact through mms from my phone to a number controlled by twilio so I could see what headers Twilio was capturing when originating directly from an iphone. That's when I noticed this important header:



                Content-Disposition: inline; filename="what-to-show.vcf"


                The key here is the "inline" argument, "attachment" doesn't work. Then my stuff came over on iOS just as I wanted. ("what-to-show" instead of "text 1"). Perfect!







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Jun 21 at 17:45









                NefNef

                1




                1






























                    draft saved

                    draft discarded
















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid


                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.

                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55387816%2fvcard-mms-file-name-is-always-text-1%23new-answer', 'question_page');

                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Kamusi Yaliyomo Aina za kamusi | Muundo wa kamusi | Faida za kamusi | Dhima ya picha katika kamusi | Marejeo | Tazama pia | Viungo vya nje | UrambazajiKuhusu kamusiGo-SwahiliWiki-KamusiKamusi ya Kiswahili na Kiingerezakuihariri na kuongeza habari

                    SQL error code 1064 with creating Laravel foreign keysForeign key constraints: When to use ON UPDATE and ON DELETEDropping column with foreign key Laravel error: General error: 1025 Error on renameLaravel SQL Can't create tableLaravel Migration foreign key errorLaravel php artisan migrate:refresh giving a syntax errorSQLSTATE[42S01]: Base table or view already exists or Base table or view already exists: 1050 Tableerror in migrating laravel file to xampp serverSyntax error or access violation: 1064:syntax to use near 'unsigned not null, modelName varchar(191) not null, title varchar(191) not nLaravel cannot create new table field in mysqlLaravel 5.7:Last migration creates table but is not registered in the migration table

                    은진 송씨 목차 역사 본관 분파 인물 조선 왕실과의 인척 관계 집성촌 항렬자 인구 같이 보기 각주 둘러보기 메뉴은진 송씨세종실록 149권, 지리지 충청도 공주목 은진현