codah's Forum Posts

  • Well done, nice art style and fun

  • I've just tried to publish a test app that simply has a single sprite on a layout.

    I've read lots of tutorials. Using XDK v 1621

    I have a Developer account

    I have an app ID, call it com.company.product

    I have a registered device (iPad)

    I have an ad hoc provisioning profile showing the same App ID, 1 certificate and 1 Device

    I have another provisioning profile (how can you tell which is ad hoc or not, only by the name I gave it??) showing the same App ID, 1 Cert and 0 devices

    I have no development provisiong profiles, as per what I've read, but I wouldn't thought I'd need one? (judging by the name)

    In the XDK I created a new project for the test app

    App ID set as above

    Version 1.8.2 (as per my existing Android version)

    Full screen

    Landscape

    iOS target 5

    Provisioning profile Ad hoc

    Ad hoc provisioning profile: set to the adhoc xxx.mobileprovision file

    Production provisioning profile: set to the other xxx.mobileprovision file

    As a first test I did not add any icons or splash screens

    I did not alter the plugins

    Build tab, build, upload

    Build page says iOS CERTIFICATE: Step complete. If i choose Edit, it says 1a: "Your CSR has been generated..." etc. and 1b: Certificate uploaded..." etc.

    I get all warnings about "no images provided" and "no splash screen".. and "An unexpected error occurred"

    Next step I will add icons and splash screens and re test.

    Thanks for any help.

    Edit: added icons and splash screens, got the errors about some further splash screen sizes, so added those images and added them to the 'intelxdk.config.additions.xml' file. No warnings now, just the same error at the end.

    imaffett can I send you the build log?

  • You do not have permission to view this post

  • Yeah I have the same version, but some splash screen sizes are not listed. Anyway I have no errors from splash screens. I'll try again tomorrow

  • So I had another go at doing my iOS app. Now it won't even build in the XDK. Instead of using a separate XDK project for iOS I'm now using the same one as I use for Android and of course setting the iOS properties including splash screens (plus the 'additional' splash screen stuff). That should be ok, right? Then I revoked my certificates and re-did them, and the provisioning files. I'm not sure what I'm doing wrong. Maybe I will submit my build log to Intel to have a look.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads

  • Many thanks for the help, it now builds successfully ! As you highlighted I had to create a mobileprovision from the certificate.

    Didn't know they had to be related to each other !

    Hi Rable could you please explain this? It seems you were missing the provisioning files, but how did you do a build in the XDK without them? Thanks.

  • codah Hi Just to let you know, when building with XDK the distribution build for IOS make sure you select IOS TARGETING 5.1.1 otherwise apple will reject the game during the upload process with the apploader. I experienced this last night and when I selected 5.1.1 it was ok. Good Luck

    Thanks. BTW I'm the one who commented on your post in G+

    Also, I'm using Cordova export in C2 instead of PhoneGap as mentioned in your doc.

  • Simple...

    When I edit the code in the evnet sheet. It would be so nice if I could select the instances by name. Especially when you access instance variables..

    InstanceName.instancevariable

    Instead of now,

    ObjectName.InstanceVariable.

    If your instance is on the layout. It is declared as available in the game for your events. Sure it makes no sense if you spawn instances in events. But whey they are placed on the layout. It would be so nice If I could access them by name instead of IID (or UID)

    And yes it is traditional programming, in Visual Stucio / xCode etc. And not drag and drop in Construct 2.

    Fair enough. Somehow it becomes natural pretty quickly to do things the Construct way Usually when I have fixed objects in a layout they will have an ID value, and sometimes I do use that in a similar way. You could have a dummy Text instance variable with values like "top", "bottom", "this one" or whatever to identify them if you wanted . Or create a really simple Behaviour with a single property 'Instance name'.

  • Ok got it.

    Thanks for your help.

    It would be nice if you could see an the instances in your inspector and give them a name.

    What tends to confuse me is that the Name property is the property of the object, not the instance.

    It would be nice if you could name instances and have them available in your events sheets as if they were instance variables ( in ordinary programming )

    This is whats confusing me.

    Now you have to pick by uid, which you cant trust because they change, so you have to save these values in an array or dictionary, and it just makes the code hard to read I think.

    So if any from the scirra team is reading this... Instance names, would be nice.

    What name would you give to your instances? Remember instances can be dynamic, not just placed at design time. You can always add an instance variable yourself to identify it in the inspector (where you already can see the instances, numbered by IID). If you're still thinking as per traditional programming, you still need to do the 'paradigm shift'

    I do agree it should be 'Type' not 'Name'

  • try this, it now shows the values and types

  • That's right. Just try it and see

  • I've updated the capx, see if it's what you want.

    edit: note the 'add key' lines should be out of the loop Updated.

  • codah I just tried that in the example I posted and it doesn't work. Can you try with my example capx and see?

    I assumed you knew how to do the rest in your actual code Have a look at the — post. You probably don't want to add instance variables to your Dict?onary like that.. what are you trying to achieve?

    edit: oh ok, try this

  • Just remove the quotes around bunny.type

  • oh well as long as you got it working!