Your comments
You will have to invite me to the portfolio if you want me to have access. You can invite me as a collaborator to your project. My email is icahill@rarewire.com
12 years ago
Tyler,
So I did some digging. Our Engine Binary on new Apps starts at 2.3.1. This is a backend version that Apple looks for to determine if the App needs to be updated. Apple requires that Apps increment to a higher number anytime a build is made.
Our Release Build Provisioner has an auto increment feature that will take care of this for you, so you shouldn't have to worry about this number.
However, this version number is not the same as the user facing on in itunes connect. That is an arbitrary number that you set when you submit a new build for approval.
Does that make sense so far?
Our system DOES NOT auto increment Ad-Hoc builds at this time, so if you were to use Test Flight it will save over any older IPAs with the same 2.3.1 version.
What I can do is create a ticket for our Dev team to try and get A) the binary version to default to 1.0 and B) to set up auto-incrementing for Ad-Hocs.
So I did some digging. Our Engine Binary on new Apps starts at 2.3.1. This is a backend version that Apple looks for to determine if the App needs to be updated. Apple requires that Apps increment to a higher number anytime a build is made.
Our Release Build Provisioner has an auto increment feature that will take care of this for you, so you shouldn't have to worry about this number.
However, this version number is not the same as the user facing on in itunes connect. That is an arbitrary number that you set when you submit a new build for approval.
Does that make sense so far?
Our system DOES NOT auto increment Ad-Hoc builds at this time, so if you were to use Test Flight it will save over any older IPAs with the same 2.3.1 version.
What I can do is create a ticket for our Dev team to try and get A) the binary version to default to 1.0 and B) to set up auto-incrementing for Ad-Hocs.
Jorge,
Video out is a feature of the device hardware and any App created in WIRE should not be affected. You just need to hook up the device to the TV using an approved cable or Apple TV and see the device screen mirrored to the TV.
Video out is a feature of the device hardware and any App created in WIRE should not be affected. You just need to hook up the device to the TV using an approved cable or Apple TV and see the device screen mirrored to the TV.
Michael,
Let me spend some time with these. I know we have a team in place to address these twitter 1.1 issues.
Let me spend some time with these. I know we have a team in place to address these twitter 1.1 issues.
Where is the version number you are referring to displaying? In our studio?
I have also updated the documentation for this. Hope that helps!
Greg,
The annotation functionality was recently overhauled and the documentation got a little out of sync. Please take a look at this example and let me know if that is what you had in mind.
The annotation functionality was recently overhauled and the documentation got a little out of sync. Please take a look at this example and let me know if that is what you had in mind.
<wire>
<classes>
<class name="annotations">
<annotation name="office" location="[param:location]" title="[param:title]" animatedrop="yes"></annotation>
</class>
</classes>
<main>
<panel name="test" width="100%" height="100%" >
<map name="map" alias="MAP" width="100%" height="100%" type="map" currentlocation="yes"></map>
</panel>
</main>
<actions>
<action name="pin" oninit="yes">
<assign property="object:MAP.region" value="38.989983 -95.292835 38.926858 -95.202026"/>
<create class="annotations" location="38.9581 -95.2478" title="University of Kansas" target="MAP"/>
<create class="annotations" location="38.965096 -95.235983" title="Pyramid Pizza" target="MAP"/>
</action>
</actions>
</wire>
Currently the PDF tag doesn't support external PDFs, so the solution here is to load the PDF using a web tag. It will have limited functionality and you can't embed other WIRE inside of the remote PDF.
I currently have a ticket open for this issue.
Hope that helps.
I currently have a ticket open for this issue.
Hope that helps.
Launch images will not display within fusebox, so you will have to create an ad-hoc or a release build to see them.
They display for a default time by Apple. You can add WIRE code to display the image longer by having a replica splash screen show up 100% oninit and then use an action to remove it after a few seconds.
They display for a default time by Apple. You can add WIRE code to display the image longer by having a replica splash screen show up 100% oninit and then use an action to remove it after a few seconds.
This has been done in the past. It is actually pretty easy to implement.
You simply create your dots as a class (with two different styles: on/off). Then present those dots where it is appropriate in your App.
In order to get them to switch when you change to another "page" you can use a concept called states.
Check out this link on a quick example of how to use states in your project:
http://www.moderndukes.com/post/34704...
You simply create your dots as a class (with two different styles: on/off). Then present those dots where it is appropriate in your App.
In order to get them to switch when you change to another "page" you can use a concept called states.
Check out this link on a quick example of how to use states in your project:
http://www.moderndukes.com/post/34704...
Customer support service by UserEcho
