IE / Spry Bug with custom error handler

Ok, as I was looking through SpryData.js I noticed these
wonderful lines:
Spry.Utils.loadURL.callback = function(req)
if (!req || req.xhRequest.readyState != 4)
return;
if (req.successCallback && (req.xhRequest.status ==
200 || req.xhRequest.status == 0))
req.successCallback(req);
else if (req.errorCallback)
req.errorCallback(req);
In particular the "errorCallback()" method interested me as I
wanted to introduce my own error handler. As I went about testing
this I came up with a quick try of:
var url = "/cfcs/mycfc.cfc?method=IsValidPath&path=" +
encodeURIComponent(sl.value + sd.value);
var optionsObj = new Object();
optionsObj.errorCallback = ShowError;
Spry.Utils.loadURL("GET", url, false, ValidateForm,
optionsObj);
And this works great in FF, but not IE. When I cause an error
to occur from ColdFusion I pass a status code of "500". In FF the
error code causes my "ShowError" function to fire, but not in IE. I
tracked it to this bit of code in SpryData.js:
Spry.Utils.loadURL = function(method, url, async, callback,
opts)
var req = new Spry.Utils.loadURL.Request();
req.method = method;
req.url = url;
req.async = async;
req.successCallback = callback;
Spry.Utils.setOptions(req, opts);
try
req.xhRequest = Spry.Utils.createXMLHttpRequest();
if (!req.xhRequest)
return null;
if (req.async)
req.xhRequest.onreadystatechange = function() {
Spry.Utils.loadURL.callback(req); };
req.xhRequest.open(req.method, req.url, req.async,
req.username, req.password);
if (req.headers)
for (var name in req.headers)
req.xhRequest.setRequestHeader(name, req.headers[name]);
req.xhRequest.send(req.postData);
if (!req.async)
Spry.Utils.loadURL.callback(req);
catch(e) { req = null; Spry.Debug.reportError("Exception
caught while loading " + url + ": " + e.message); }
return req;
Apparently running (req.xhRequest.send(req.postData);) in IE
will throw an error if the requested page throws an error status
code. This causes the try/catch in the Spry function to catch the
IE error and never allows my own error handler to run. Hopefully a
fix for this will be in the works because I really like the idea of
being able to use my own error handler.
--------Edited after initial post.--------
Ok, I figured out another item of interest. My requests
earlier were set to "async = false". If I set "async = true" then
it does work. I realized that because I was using sychronous mode
and IE was throwing the error, it was preventing the call to the
"Spry.Utils.loadURL.callback" method from occuring, while asynch
mode uses the onreadystatechange to call the function and thus
causes my own error handler to function. I am still interested to
know if there is a bug here somewhere and if it is just IE or Spry
or both. Looking forward to reading any posts.

Hi WraithBudde,
Thanks for all the details. In my opinion this is indeed a
bug in Spry for the synchronous case. I'll file a bug and fix it.
> You know you love me.
Heh, yeah, I love anybody who takes the time to report bugs
... especially when they've narrowed it down to the exact set of
lines in the source.
Once again ... THANKS!
--== Kin ==--

Similar Messages

  • Custom Error handling in DataSheet View with pop-up message or label controls or HTML

    I have a requirement in which DataSheet view is used to bulk edit or input list items and handle validations while in the process.
    We have validations done in event recievers before creating the list item. But could not provide a pop up or message with summary of all validation errors. these are buiness custom validations.
    Is there a way to custom error handle datasheet view? Is there a way to invoke a UI in context from event recievers?

    I have a requirement in which DataSheet view is used to bulk edit or input list items and handle validations while in the process.
    We have validations done in event recievers before creating the list item. But could not provide a pop up or message with summary of all validation errors. these are buiness custom validations.
    Is there a way to custom error handle datasheet view? Is there a way to invoke a UI in context from event recievers?

  • ADF11g+ Custom error handler

    Hello,
    I am using Build JDEVADF_11.1.1.2.0_GENERIC_091029.2229.5536
    I defined the custom error handler as mentioned in the ADF development guide.Facing weired issue when AM method is called from task flow.
    e.g,
    AM method
    public showSuccessMessage(){
    this.getDBTransaction().addWarning(new JboWarning("Hello Sample message from AM"));
    Above method is called from taskflow and corresponding action is specified in the page.I have task flow ErrorHander activity defined for the task flow also.When I click the button to call the AM method,Jbo warning raised in AM and catched by the task flow error handler and after this control is passed to CustomErrorHandler and message shows properly.But this happens only first time.After that control never goes to custom error handler. Am I missing some thing??
    Any idea why??
    Thanks
    RB

    Hi Frank,
    Thanks
    What I noticed is,
    Case:1
    when warning is raised using the addWarning api from AM, binding layer throws exception of type Warning,catches in task flow error handler and directly goes to get getDisplay message method of the custom error handler which is defined in databinding.cpx only once.After that it catches in taskflow error handler and never goes to custom error handler defined in data binding.cpx
    Case2:
    When I raised it as throw new JboException flow goes reportException of custom error handler and which calls the getDisplay message.In this it even not going to task flow error handler.
    If you can confirm this is expected behavior or it is bug that would be great,it helps us define the exception handling framework.
    Thanks
    RB

  • Custom error handler examples and/or instruction

    I'm finishing up an application and would like to customize some of the error reporting.
    I've started playing around with the custom error handler VI's with some success. I would, however, like to see some examples from people who know what they are doing (unlike me).
    As always, your feedback is appreciated.
    Todd

    Look at this message.
    http://forums.ni.com/ni/board/message?board.id=170&message.id=45649
    Do a search for "General Error Handler" and you'll find some others.
    I'm also trying to find a simple way to define custom error codes and descriptions in an error cluster. I can produce my codes easily enough using the vi posted by Aristos Queue in the message noted above. I can also display my user-defined descriptions using a dialog, but I haven't found an easy way to make the user-defined descriptions in the array appear in the error cluster.
    Any help on this would be appreciated.
    Attachments:
    Error_Demo.vi ‏37 KB

  • ADF Custom error handler not working.

    Hi All,
    i am using jdev version 11.1.1.5.0. i have created one custom error handler class in model layer which extend DcErrorHandlerImpl class.
    and do the entry in Databinding.cpx file
    *<Application ErrorHandlerClass="mypackage.classname"/>*
    i have override getDisplayMessage(BindingContext ctx, Exception ex) method to show SQL Exception which comes from database table trigger.
    code is following-
    package com.in.jagran.view.services;
        import java.sql.SQLException;
        import oracle.adf.model.BindingContext;
        import oracle.adf.model.binding.DCErrorHandlerImpl;
        import oracle.jbo.JboException;
        public class AclasErrorHandler extends DCErrorHandlerImpl {
          public AclasErrorHandler(boolean setToThrow) {
            super(setToThrow);
            System.out.println("Inside Error Handler class");
          public AclasErrorHandler() {
              super(true);
           // this(true);
           * Returns the message that will be reported to JSF for each error that occurs.
           * Returning "null" is the way the custom error handler signals that a given exception
           * should not be reported to the client.
          @Override
          public String getDisplayMessage(BindingContext ctx, Exception ex)
            if (ex instanceof oracle.jbo.ValidationException) {
              return super.getDisplayMessage(ctx, ex);
            else {
              // Extract and return the error message that has to be displayed
              Exception exception = ex;
              String message = "";
              // If this exception is an instance of JboException,
              // try to find the cause by recursing over the eventual causing exceptions
              if (exception instanceof JboException)
                Throwable[] exceptionList = ((JboException)exception).getExceptions();
                while (exception instanceof JboException
                        && exceptionList != null && exceptionList.length > 0)
                  exception = (Exception)exceptionList[0];
                  if (exception instanceof JboException) {
                    exceptionList = ((JboException)exception).getExceptions();
              // *** Special processing of SQLExceptions
              if (exception instanceof SQLException) {
                message = exception.getMessage();
                // Ignore the lines in the error message that indicate the line number in the PLSQL code that the error resulted on.
                int ind = message.indexOf("ORA-06512");
                if (ind > 0)
                  message = message.substring(0, ind);
              // *** If the the reason for the JboException was data creation exception then display the message
              // of the top JboException (i.e. JBO-*****: Invalid numeric value, date format or time format)
              else if (exception instanceof NumberFormatException || exception instanceof IllegalArgumentException) {
                // Report the top exception
                message = ex.getMessage();
              // Otherwise report the message of the lowest exception in the hierarchy
              else {
                message = exception.getMessage();
              return message;
        }but it is not working for me.
    thanks in Advance.

    yes i have used dubugger.
    i have set break point to following line-
    return super.getDisplayMessage(ctx, ex);
    if (ex instanceof oracle.jbo.ValidationException) {
            return super.getDisplayMessage(ctx, ex);   
    }when atttribute validation done like i have attribute of type number and i have done the validation "must be greater than 0" now when i have given negative value control go to above line.
    and i have added following code also in handler class
            @Override
               public void reportException(DCBindingContainer dCBindingContainer,
                                           Exception exception) {
    System.out.println(exception.getMessage());
                       super.reportException(dCBindingContainer, exception);
                   }now when i have done commit operation control go to here and println statement print follwoing error on log window.
    JBO-26041: Failed to post data to database during "Rollback to Savepoint": SQL Statement "null".

  • Custom Error Handling

    Hello,
    I would like to create a custom error handler in a model file similar to the ErrorHandlerExample.seq.
    In my case, I will be handing errors genereated in several different dlls.  We are trying to avoid writing wrappers around the dll functions to fill in the TestStand error strings.  However, this information is available by calling a "get error message" function in the dll.  Since I have more than one dll and more than one handle that I will need to check the errors for, I need to know the information about the step that caused the error.  Is there a way to get more information about the step that caused the error?  I might have a dll function call that had the format: 
    kiOpenVSA(StationGlobals.KiManager, StationGlobals.VsaSession, StationGlobals.VsaResourceString, StationGlobals.DisplayEnable, StationGlobals.SendInitCommands)
    Based on the parameters of the function call, I would be able to call the correct error handling function.
    Thanks,
    Mike
    Solved!
    Go to Solution.

    Hi Mike,
    If you want to pragmatically get the name of the DLL file, DLL function and parameters that were called in a previous step, you will first need to reference the step in which the DLL call was made and use the following TestStand API.
    Assuming that the DLL was called in the previous step you can use the following expressions using TestStand 4.1.
    Access the dll function expression
    RunState.PreviousStep.Module.CommonCModule.FunctionCall
    Access the dll function name
    RunState.PreviousStep.Module.CommonCModule.FunctionName 
      Access the parameters
    RunState.PreviousStep.Module.AsDllModule.Parameters.item(index)
    Note that if you are using an older version of TesStand, these functions may not work and you may have to use the ActiveX/COM steps to access this information.
    I hope this helps.  
    Message Edited by S_Hong on 02-10-2009 05:02 PM
    Message Edited by S_Hong on 02-10-2009 05:07 PM
    S_Hong
    National Instruments
    Applications Engineer

  • Using the error routines with custom errors...

    How do I cause the error handlers to recognize a custom error? I used
    this page
    (http://zone.ni.com/devzone/conceptd.nsf/webmain/DE4F036F22C4B9F286256FEE0010B6FD)
    to create custom error codes but now how do I raise one while a VI is
    running?
    Thanks,
    Dave

    Hi Dave,
    All you need to do is wire an error cluster with a 'status' of True and one of your custom error codes as the 'code' into the General Error Handler VI, and it should pop up an error dialog with your custom error specified.
    If you're still having trouble, let me know.
    -D
    Darren Nattinger, CLA
    LabVIEW Artisan and Nugget Penman

  • Problems with Custom Exception Handler

    Hi,
    I have defined a custom exception handler for my workflow (WebLogic Platform
    7).
    I have a workflow variable called 'count' , which gets incremented for every
    time an exception occurs.
    The exception handler checks if the count is less than 3(using evaluate
    condition),
    if yes then it executes the action "Exit Execption Handler and retry"
    else
    it executes the action "Exit Execption Handler and continue"
    The Workflow simply hangs, nothing on the console , the worklist from which
    i call it hangs too.
    Has anyone managed to use this kind of exception handling?
    Thanks in advance,
    Asif

    bill0 wrote:
    > Thanks for all the help but still no luck.
    >
    > The directory is d:\wSites\GBMain\html\CFMS> and I am
    mapped to it as x:\CFMS.
    > Most of the cfm files are in CFMS but Application.cfm is
    1 directory up in
    > html. I have tried misscfm.cfm in both html and CFMS but
    had no luck having it
    > find a non existant template referred to in a cfinclude
    or a form's action
    > attribute. The default ColdFusion error handler is what
    shows. The missing
    > template handler box says /misscfm.cfm. Misscfm.cfm is
    text followed by a
    > <cfabort>. We use ColdFusion MX6.1
    >
    > I hope that is enough information to figure what am I
    missing and/or doing
    > wrong.
    >
    >
    Is the 'misscfm.cfm' file somewhere in the
    'd:\wSites\GBMain\html\CFMS\'
    directory. I will presume this is the 'web root' as defined
    in your web
    server (IIS or Apache or built-in or ???). The missing
    template handler
    file needs to be in the ColdFusion root. This is going to be
    a
    directory such as
    '{drive}:\JRun4\servers\{server}\cfusion-ear\cfusion-war\misscfm.cfm'
    for J2EE flavors OR '{drive}:\CFusionMX\wwwroot' for Standard
    I think.
    It has been a very long time since I have dealt with
    Standard.
    This is probably completely different from the above web
    root. That is
    the point I am trying to get across. ColdFusion has TWO roots
    where it
    will look for a CFML file. But the Missing and Sitewide
    templates can
    only be in the ColdFusion root listed above, they will not
    work in the
    web root.
    HTH
    Ian

  • LV7.1 Strange behavior with Automatic Error Handling occuring when it shouldn't [LV 7.1 Pro on WinXP for Tablet PC's]

    [LV 7.1 Pro on WinXP for Tablet PC's]
    I recently let a rather large LV app of mine run in the development environment while I was out for a couple of days. Upon returning I found that the app had hung for ~22 hours waiting for an answer to an Automatic Error Handling (AEH) dialog proclaiming an Error 7 in New File without any indication of the VI hierarchy that called New File.  I set about ensuring that AEH dialogs would not pop up and have not been able to discover how I could have possibly received one in the first place.
    Subsequent investigation revealed:
    Neither AEH option in Options>Block Diagrams were checked.
    Network problems had occurred around the time that the app had hung.  All file paths are network paths when running in the development environment, so the cause of the error was most likely valid, even if the AEH dialog appearance wasn't.
    My app has only one instance where the New File primitive is used by me. That subVI and all others above it in the hierarchy DO NOT have the AEH property enabled.  The error out cluster of New File in my subvi is wired.
    My app has three instances where New File is called from a vi.lib vi (Open/Create/Replace File.vi, Open Config Data.vi, and Prompt Web Browser Path.vi), none of which have the AEH property enabled.  Nor does any of their calling VI's.  All three instances also have their error out cluster wired.
    A utility to examine the AEH property of all VI's (with all top level and dynamic VI's loaded) in memory reported that only 1 of 308 vi's ( RGT Does File Exists.vi from the Report Generation Toolkit) had that property true.  That vi has no subVI's other than the File/Directory Info primitive and no calling VI's in common with any of the vi's that call New File, except a top level VI.
    As long as 'Enable automatic error handling dialogs' remains unselected in options>block diagram, I am unable to get an AEH dialog for either the New File or File/Directory Info primitives in a test VI with AEH property enabled and their error out clusters unwired no matter what invalid path I pass to the functions.  As soon as the options>block diagram>Enable AEH dialogs' is selected, both primitives fire AEH dialogs with no error out wired and don't when wired. i.e. works as advertised.
    In other words I can find no reason why I should have gotten the problem AEH dialog...
    I cannot afford for this app to hang because of a network problem, other portions of the app that were running concurrently correctly handled the error and, had the AEH dialog not appeared, the app would have made corrections or shutdown in an orderly fashion.
    Any ideas?

    Very good.
    Write Characters to File.vi>Open/Create/Replace File.vi>New File
    New File throws the error.  Open/Create/Replace strips the hierarchy from the source of the error.  Write Characters passes it to the General Error Handler.  I never looked above O/C/R file in the hierarchy except for enable automatic error handling property.  The tip-off should have been to realize that O/C/R file was stripping the hierarchy from the error and look above that. 
    The real irony is that Write Characters was being used to log error cluster data to an error log file...
    Save as... Copy without updating... the OEM 'Write Characters to File' is gone from this app.
    Thanx (a bunch)

  • Issue with SRDemo error handling

    Hi All,
    Glad the forums are back up and running. In debugging some error-handling issues in our own application, I found an issue in the error handling code of SRDemo. I thought I'd post the issue here, as many of us (myself included) use some SRDemo code as the basis for our own applications.
    The issue can be found in the oracle.srdemo.view.frameworkExt.SRDemoPageLifecycle class, specifically in the translateExceptionToFacesErrors method. I'll show the code that has the issue first, and explain the issue afterwards:
            if (numAttr > 0) {
                Iterator i = attributeErrors.keySet().iterator();
                while (i.hasNext()) {
                    String attrNameKey = (String)i.next();
                     * Only add the error to show to the user if it was related
                     * to a field they can see on the screen. We accomplish this
                     * by checking whether there is a control binding in the current
                     * binding container by the same name as the attribute with
                     * the related exception that was reported.
                    ControlBinding cb =
                        ADFUtils.findControlBinding(bc, attrNameKey);
                    if (cb != null) {
                        String msg = (String)attributeErrors.get(attrNameKey);
                        if (cb instanceof JUCtrlAttrsBinding) {
                            attrNameKey = ((JUCtrlAttrsBinding)cb).getLabel();
                        JSFUtils.addFacesErrorMessage(attrNameKey, msg);
                }Now, this bit of code attempts to be "smart" and only show error messages relating to attributes if those attributes are in fact displayed on the screen. It does so by using a utility method to find a control binding for the attribute name. There are two issues with this code, one obvious, and one that is a bit more subtle.
    The obvious issue: if there is a binding in the page definition, it doesn't necessarily mean that the attribute is shown on the screen. It's a good approximation, but not exact.
    The other issue is more subtle, and led to errors being "eaten," or not shown, in our application. The issue comes if you are using an af:table to display and update your data. In that case, the findControlBinding will not find anything for that attribute, since the attribute is contained within a table binding.
    Just posting this as a word to the wary.
    Best,
    john

    somehow, this message got in the wrong thread....
    Hi Frank,
    Yes, I simply scripted it out this way to contrast the behaviour if the first attribute was read-only vs not read-only. I found the issue on a page in our app that was simply drag-and-drop the VO from the data control on the page.
    It's quite annoying, because our particular use case that hit this error is a "save" button on the page. If the commit operation doesn't return any errors (and it doesn't in this use case!), we add a JSF message saying "save successful" - then the attribute errors are further added later in the page lifecycle, so we get 3 messages: "Save successful" and "Fix this error" and "Tried to set read-only attribute" - quite confusing to the end-user when the only message they should see is "fix this error."
    At any rate, the fix is to simply re-order the attributes in the page definition - that doesn't affect the UI at all, other than to fix this issue.
    John
    it was supposed to be something like:
    Hi Frank,
    Thanks for the reply. I was simply posting this here so that people who use the SRDemo application techniques as a basis for developing the same functionality in their own apps (like me) can be aware of the issue, and avoid lots of head-scratching to figure out "what happened to the error message?"
    John

  • Flex bug in global error handling

    My application's global error handler (uncaught error handler) works mostly, but I found a case where it doesn't work, but should.  Before I filed an official bug report I wanted to post the issue here.
    Here is the issue: in a module, ErrorEvents that are not listened for  and are dispatched by a Flex component are never caught in the application's uncaught error handler. 
    I have a sample project that demonstrates this.  Here is the module in my test case:
    <?xml version="1.0" encoding="utf-8"?>
    <s:Module xmlns:fx="http://ns.adobe.com/mxml/2009"
                 xmlns:s="library://ns.adobe.com/flex/spark"
                 xmlns:mx="library://ns.adobe.com/flex/mx">
    <fx:Script>
        <![CDATA[
            private function onClickSparkDispatch():void {
                dispatchEvent( new ErrorEvent( ErrorEvent.ERROR, false, false, "test" ) );   // this isn't caught in the uncaught error handler
            private function onClickNonSparkDispatch():void {
                var nonSparkDispatcher:EventDispatcher = new EventDispatcher();
                nonSparkDispatcher.dispatchEvent( new ErrorEvent( ErrorEvent.ERROR, false, false, "test" ) );  // this is caught in the uncaught error handler
        ]]>
    </fx:Script>   
        <s:HGroup>
            <s:Button label="Module Spark Dispatch (broken)" click="onClickSparkDispatch()" />
            <s:Button label="Module Non-Spark Dispatch" click="onClickNonSparkDispatch()" />
        </s:HGroup>
    </s:Module>
    Using Flex 4.6
    My application statically links in the Flex SDK ("merged into code" in Flash Builder).
    My applications works around these two exsiting bugs:
         https://bugs.adobe.com/jira/browse/SDK-28018
         http://blogs.adobe.com/aharui/2011/04/catching-uncaughterror-in-flex-modules.html
    Is this a bug?
    Thanks,
    Rick

    It’s been reported.  Here is more information and a workaround. http://blogs.adobe.com/aharui/2011/04/catching-uncaughterror-in-flex-modules.html

  • Receiver Feedback with no Error Handling (Input Design Requested)

    Hi Community,
    Today we have a pretty standard integration scenario that takes in flat files and converts them to Idocs for target SAP systems.  We are looking to redesign the current IDoc interface (posts a customized FIDCC1) under the principle that IDocs in errors on target are always corrected by a change in the source, so essentially we want to report errors back to the source and completely delete the IDoc.  I guess this looks like a synchronous call?, but I want to remain as loosely coupled for this.  Since we also process these files in batches (i.e. each file contains 1 to many invoices), we would like to return the results back to the source based on each file.  For example, the message back to the source (in email so a user can act on it, not a system) could be:
    a) file failed because structure is incorrect (like an XSD type check).
    or of the file makes it through XI,
    b) list of invoices failed because xxx is incorrect and list of invoices that processed.
    We are open to using proxies, any kind of IDoc error handling that could do this, workflows, status idocs, etc.  Every option is on the table. 
    Thanks!
    Peter

    peter
    if u are open to proxes then u might haveone interface that will send the data to proxy and thru proxy u update the idoc....if idoc goes fpor an error u can have another interface triggered that will update/delete the soruce data...for this u might need to pass the soruce files details to proxy and back

  • How does BPEL Fault Management Framework gel with ESB Error Handling ?

    I see that BPEL 10.1.3.3 has pretty neat Fault Management Framework (although I have to admit it is not very well advertised).
    The next logical question is: what about ESB ? Would that help in ESB error handling ? I understand that ESB has its own Error Hospital etc.; however, we have to constantly grapple with two distinct paths for any piece of integration functionality (1. ESB 2. BPEL). I guess, all of this will be moot in the 11g timeframe. Still wondering if anyone out there has somehow unified error handling for these two distinct offerings ?

    It's not available in ESB, you have to implement/extend that by your self. Off course in the next release everthing will be better :-)
    But, if you are able to use Oracle AIA (http://edelivery.oracle.com) You could use Oracle AIA Foundation, that has a fault 'hospital' implemented both for BPEL and ESB.
    Marc
    http://orasoa.blogspot.com

  • Spry Accordion with custom scrollbar

    I'm trying to find a Spry Accordion with a custom scrollbar.
    There are other accordion scripts out there but I am most
    comfortable working with the Spry script. I cant seem to find any
    of these with a custom scrollbar. Can someone here help?

    Mr. Andersson wrote:
    > I'm trying to find a Spry Accordion with a custom
    scrollbar. There are other
    > accordion scripts out there but I am most comfortable
    working with the Spry
    > script. I cant seem to find any of these with a custom
    scrollbar. Can someone
    > here help?
    Spry has no custom scroll bars. Currently Spry (as of 1.6.1)
    doesn't have drag and drop which would be required for a custom
    scroll bar. Best you might be able to do would be to try to style
    the browser provided scroll bars, but that's not valid CSS, and I
    know that Firefox doesn't show the styled scrollbars (IE does).
    Take a look at this page in IE:
    http://www.iconico.com/CSSScrollbar/
    Danilo Celic
    |
    http://blog.extensioneering.com/
    | WebAssist Extensioneer
    | Adobe Community Expert

  • Possible iPhone bug with custom recurring day schedule?  Need help.

    In Microsoft Outlook I have a 64 day schedule that is set up as single all day recurring events each day. Each day of the 64 day schedule recurrs every 64 days. Day 1 recurrs every 64 days, day 2 recurrs every 64 days, etc., etc.
    When I synced this to an iPhone, each day had an incorrect custom recurring day set at every 18 days. This, of course threw off the whole schedule. After doing some testing, I found out that a custom recurr of 45 days worked, a custom recurr of 46 days told the iPhone it recurred every 1 day. 47 day recurr did the same thing. 48 day recurr told the iPhone it recurred every 2 days, 49 day recurr became 3 days, 50 became 4 days, 51 became 5 days...64 became 18 days.
    Is this indeed a bug with iPhone or is there something I can do for a single 1 day event recurr every 64 days? And, why is there no custom setting when setting up an event on the iPhone?

    ICKIER wrote:
    Is this too complicated for a reply?!
    Apparently, no one has a solution for you. It may be a bona fide bug. You can let Apple know about that:
    http://www.apple.com/feedback/iphone.html.

Maybe you are looking for