I created a simple demo passbook pass in iOS 6. I emailed it to myself and it works fine. Now I need to share it with people. I uploaded the .pkpass file to the server but safari is not able to recognize the file format or mime type and hence it does not download it.
Any ideas how can I share it?
Safari should recognise these.
I think you probably need to add the MIME type to your web server, so it knows how to present the file to visitors.
Edit: the MIME type you need to add to your web server is application/vnd.apple.pkpass
Passbook is only availiable on the iPhone 5 or phone users that have upgraded is iOS6. It is also available on the latest OS X Mountain Lion 10.8.2 release.
If the person doesn't have any of these, when they see it in their email, it will just show the .pkpass file as is. If they have Passbook on their device, it will do some graphical markup to it and they can click to add it to Passbook.
The MIME type has to be supported by your email server, but since you received the pass, it appears your server supports it, or doesn't care. In my case, we had issues with Amazon Web Services Simple Email Services as their WebAPI wasn't accepting files of type:
application/vnd.apple.pkpass
Which has been remedied.
https://forums.aws.amazon.com/thread.jspa?messageID=384277
To download a passbook file in Safari (mobile and desktop), you have add the correct mimetype to your server.
To do so, you can simply create an .htaccess file (or edit the existing one) and append the following line:
AddType application/vnd.apple.pkpass .pkpass
This will do the magic. After this change, if you'll click on a link <a href="..."> that points to a .pkpass file using Safari mobile on your iPhone it will automatically open it with Passbook.
I think that the pkpass files will only be recognised by:
Devices running iOS6 and above (i.e. with the passbook App installed)
Safari on OSX 10.8.2 (or above)
Edit: Google Chrome Version 23.0.1271.91 and above on iOS6 now also supports direct download of .pkpass files
Related
I am trying to build an action messaging extension with a task module implementation which uses a URL attribute to load the page. Attached is the screenshot of the task module code which was generated by Yeoman Teams generator.
The popup comes up blank. So it means it's not loading the HTML file path, but if I open Chrome and try to load the URL, it works fine.
Also instead of using URL if I use an adaptive card it works fine. Only the URL part doesn't load on the popup. Attached is another screenshot of the popup inside teams:
What could be wrong with the code?
The other answer is correct in that your url needs to be reflected 100% correctly in your manifest. However, there are a few things that you need to be clear on:
It's not per se the address of the BOT that's important, but rather the address of the web page itself that needs to be listed in your safe domains list in your manifest. In your case, they're hosted in the same endpoint, but they might not be in your final solution, depending on how you end up hosting this.
While you're developing locally, rather use App Studio. That way, you don't need to fiddle with the zip file every time - you can just change it in App Studio and immediately redeploy with the updated URL
Every time when you compile and run the project, a new hostname is generated since ngrok free license is used in the yo teams scaffolding, which makes the app to reference to the old URL.
You need to uninstall the app from the Teams app store under your organization and upload the new app from the package folder .zip (Only after gulp ngrok-serve)
If it still does not work, check the below
Unzip the package file and verify the manifest whether it's pointing to the right hostname of the action html page
Go to http://localhost:4040 to inspect the ngrok tunnel traffic that should give more info on the routed requests.
I'm working with an extension for chrome, and I'm supposed to use the Id of the extension.
I'm able to get the Id from the developer mode (it's an unpackaged extension).
So my doubts are:
When I publish the extension on the chrome extension store everyone will have a different Id?
If yes, how could I access it via code? (react.js)
I am trying to load a simple .txt file content with a Chrome App (using file: protocol); I need to show its content for the user in a <div>. I need to open the file from a path typed in a input text (or defined in a string variable).
The flag --allow-file-access-from-files works fine when I load my .txt file content through Chrome browser. However, when I try to do the same with my Chrome App launcher (I have applied --allow-file-access-from-files flag on it), it keeps telling
Cross origin requests are only supported for protocol schemes: http, data, chrome, chrome-extension, https, chrome-extension-resource.
I dont know if I am missing something or if it is impossible for chrome app.
My user will work with the app in Windows platform.
I finally figured out that --allow-file-access-from-files does not work at all in my case.
I started coding using fileSystem and made something like the recomended in this question, following the main example. Now I am able to work with files in a directory asking the user to choose it only one time.
I'm developing an extension (and website) for a friend who needs to make different profiles for people, comparable to an intranet or online address-book.
The extension works almost great, but I'd like to have an option to upload profile pictures at the frontend in the create and edit action.
The example of Helhum on Github somehow doesn't work on Typo3 7.4. It tells me
An error occurred while trying to call Helhum\UploadExample\Controller\ExampleController->createAction()
image:
Object with identifier "1:/content/" does not exist in storage
Problem might be that you do not have that folder. You can try with default user upload folder like:
UploadedFileReferenceConverter::CONFIGURATION_UPLOAD_FOLDER =>
'1:/user_upload/'
I have a web server on port 80 and port 81. IE can connect to the server on either port. This worked fine until I installed an application with a file type (.TPJ) that had a MIME type of text/xml on the client PC. At that point IE no longer opened the web site, but offered to download a file serverName.TPJ. The file contained the correct information from the web site.
I changed the installer for the application so it didn't register the MIME type. Now IE on the client PC offers to download a file with unknown file type. Note that the application has never been installed on the server PC.
The problem occurs with IE7. It doesn't occur with Firefox, Safari, or Chrome.
Does anyone know how to work around this?
I found the answer. There is a left-over entry in the registry for the text/xml MIME type. It can be restored to the default value by re-registering the MSXML3.DLL.
regsvr32 msxml3.dll
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\MIME\Database\Content Type\text/xml]
"CLSID"="{48123BC4-99D9-11D1-A6B3-00C04FD91555}"
"Extension"=".xml"
"Encoding"=hex:08,00,00,00