Getting error over plays tore
Digital Asset Links JSON file failed
brightness_1
Add a Digital Asset Links JSON file to all the failed domains how to resolve this problem
Digitally i am generating assetlinks.json using **https://developers.google.com/digital-asset-links/tools/generator **
Now what should be next step Is there is need to create assetlinks.json file in android project directory or need to publish app again over google play store
Related
I have a continuous web job and we have a certificates which are included as part of build. Build contains certificates inside a certificates but I got a below error
Could not find file
D:\local\Temp\jobs\continuous\MyWebJobProject\idyunnoo.f2h\Certificates\INT\XXXX.p12
in actual build certificates folder present in MyWebJobProject folder , folder structure is
MyWebJobProject\ Certificates\INT\XXXX.p12
I am not sure why code is checking inside idyunnoo.f2h folder and not sure when this kind of folders will create in azure web job
in my code we using AppDomain.CurrentDomain.BaseDirectory to find path of Certificate
Path.Combine(AppDomain.CurrentDomain.BaseDirectory, "Certificates\Production\XXXX.p12");
Take my screenshot as an example, when you post your webjob, make sure that your certificates folder is under the Debug folder, and then package the Debug folder. There is no problem with your code. I tested it with your method. It should be the wrong path for the certificate.
Your folder structure is MyWebJobProject\Certificates\INT\XXXX.p12, So you should build your program. And rename Debug to MyWebJobProject, then compress files into zip format for upload. Make sure Certificates folder is under MyWebJobProject folder.
I have developed web app using .NET Core 2.0. Now I want to deploy this app in Azure Marketplace so anyone can use this app. To deploy the app I have created package which will contain below 2 files.
mainTemplate.json
createUIDefinition.json
And I have uploaded the package as shown in below image.
But it shows error:
Package acceptance validation error: AzureAppAssetRequiredFileNotFound Could not find required file in package createUiDefinition.json File path: createUiDefinition.json Code: PAC-AzureAppAssetRequiredFileNotFound
I have tried to fix this issue but I was not able to make it work. Has anyone faced this issue or anyone know the solution please guide me.
Thanks
Usually this happens when your ZIP file contains folders, and in those folders you have the artifacts such as createUiDefinition.json.
To fix, make sure createUiDefinition.json is at the root of the ZIP archive and not in any subfolders.
Iphone app was created using an online platform which no longer exists. Probably a year ago. I am trying to upload to https://www.diawi.com/ now, so that the app can still be used in some fashion.
I originally received an error stating "Error with Payload Directory" and moved the .app folder into a folder called "Payload" and now it seems not be able to find the Info.plist file. Any assistance? I am a bit out of date in my app experience.
App.ipa is located at http://beveragedist.com/app/Payload.ipa
for anyone who can help me troubleshoot the internal file structure.
I am trying to archive my MonoTouch app and to supply it to our testers using Apple's/Xcode's organizer.
Can somebody tell me how to do that? In ObjC projects I can archive an application. But how can I achieve the same in MT/MonoDevelop?
My starting point was this documentation:
http://developer.apple.com/library/ios/#documentation/Xcode/Conceptual/iphone_development/145-Distributing_Applications/distributing_applications.html
René
The archive that Xcode provides is in the form of an .ipa file. This is a glorified zip file with a certain expected file structure.
The .ipa is made up of the following components:
A folder named "Payload", which contains the compiled
(release/iPhone) .app
a 57x57 .png icon file (which is displayed while the app is being
downloaded)
a 512x512 .png file of the icon once again - however this has to
renamed itunesartwork with no extension
iTunesMetadata.plist - this contains information about the app,
such as copyright name, genre, itemname, softwareIconNeedsShine (you
can google what information this needs).
The way I package up our .ipa, is I have a folder called "App Packaging" which has all of these components already in, and I simply update the .app file whenever we do an upload, "Compress..." then rename the file to x.ipa (OS X will ask if you want to use this extension, make sure you select ("use .ipa" !).
You can then send the file to the testers to install via itunes. If the testers are all testing on devices that are iOS 4.0+ then it is possible to distribute this over the air as well but I can go into that only if you would like me to?
EDIT - Over the air distribution
It is possible to do over the air distribution of apps as well. We use it for distribution of an enterprise app we develop but it is possible to use it for testing purposes as well. It should be noted here that in order for the app to installed, the device needs to be included in the provisioning profile you signed the app with (but you knew that already!).
In order to do over the air, you need 3 things:
the .ipa file we created earlier.
a 57x57 .png icon file (same as the one included in the .ipa preferably)
a file called "Manifest.plist"
The Manifest plist contains the following structure/information:
You'll then want to upload all of these files to your website/intranet etc. In order to download the app, you'll need to create a page that points to the Manifest.plist file and then then iOS takes care of the rest and downloads the app from the location specified in the manifest.
There is now a much much easier way. On the Project menu in MonoDevelop, choose Publish to TestFlight.
You'll need a free TestFlightApp.com account, but it works great!
Our firm has begun building MonoTouch iPad/iPhone apps for enterprise deployment.
How do I take the app and create a *.ipa file for upload to our MDM server?
An .ipa file is basically a glorified .zip file. There are a couple of routes you can go down:
Export the project to xcode and under "Build" click "Build and Archive" - fill in the appropriate details and the project should create the .ipa for you as expected.
If this isn't an option, (which it isnt for us, so this is the method I've used, to great success) you can simply create all the components that go into the .ipa and right-click, "Compress..." in Finder.
The .ipa is made up of the following components:
A folder named "Payload", which contains the compiled (release/iPhone) .app
a 57x57 .png icon file (which is displayed while the app is being downloaded)
a 512x512 .png file of the icon once again - however this has to renamed itunesartwork with no extension
iTunesMetadata.plist - this contains information about the app, such as copyright name, genre, itemname, softwareIconNeedsShine (you can google what information this needs).
The way I package up our .ipa, is I have a folder called "App Packaging" which has all of these components already in, and I simply update the .app file whenever we do an upload, "Compress..." then rename the file to x.ipa (OS X will ask if you want to use this extension, make sure you select ("use .ipa" !).
With the current Monodevelop (2.8.6.5) and Monotouch (5.2.5) it is as easy as right clicking on your project -> options -> iPhone IPA Options -> check Build ad-hoc/enterprise package (IPA) for the desired configuration.
We created a special configuration called Distribution which builds using the Distribution Certificate and In House Distribution Profile.
Luke, I like your answer and have given you the credit. I am adding some more details for my own, and others, notes.
Use SpotLight to find one of your own MonoTouch apps. Search on ".ipa".
Rename it to SomeThing.Zip
Unzip it.
You can then use the structure of the unzipped folder to edit then rezip.
Just another way to get an IPA that made it easy for me, drag your .app file onto your itunes library and sync your device. ITunes then creates a copy of the app as an .ipa file in the user/music/itunes/itunes media/mobile applications. This can then be distributed much easier than the .app file.